psyc-mirrors/libpsyc
1
0
Fork 0
mirror of git://git.psyc.eu/libpsyc synced 2024-08-15 03:19:02 +00:00
Code Issues Releases Wiki Activity

related work added

Browse source
This commit is contained in:
psyc://psyced.org/~lynX 2011-05-23 16:52:44 +02:00
parent 803d56edab
commit 76ca6af4f5
1 changed files with 28 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

29
bench/benchmark.org
View file

@ -164,6 +164,7 @@ extensibility of text-based protocols and still provides for enough
data structuring to rarely require the use of other data formats. data structuring to rarely require the use of other data formats.
* Criticism * Criticism
Are we comparing apples and oranges? Yes and no, depends on what you Are we comparing apples and oranges? Yes and no, depends on what you
need. XML is a syntax best suited for complex structured data in need. XML is a syntax best suited for complex structured data in
well-defined formats - especially good for text mark-up. JSON is a syntax well-defined formats - especially good for text mark-up. JSON is a syntax
@ -173,14 +174,23 @@ derivate of RFC 822, the syntax used by HTTP and E-Mail, and is therefore
limited in the kind and depth of data structures that can be represented limited in the kind and depth of data structures that can be represented
with it, but in exchange it is highly performant at doing just that. with it, but in exchange it is highly performant at doing just that.
So it is up to you to find out which of the three formats fulfils your So it is up to you to find out which format fulfils your
requirements the best. We use PSYC for the majority of messaging where requirements the best. We use PSYC for the majority of messaging where
JSON and XMPP aren't efficient and opaque enough, but we employ XML and JSON and XMPP aren't efficient and opaque enough, but we employ XML and
JSON as payloads within PSYC for data that doesn't fit the PSYC model. JSON as payloads within PSYC for data that doesn't fit the PSYC model.
For some reason all three formats are being used for messaging, although For some reason all three formats are being used for messaging, although
only PSYC was actually designed for that purpose. only PSYC was actually designed for that purpose.
Another aspect is the availability of these formats for spontaneous
use. You could generate and parse JSON yourself but you have to be
careful about escaping. XML can be rendered manually if you know your
data will not break the syntax, but you can't really parse it without
a bullet proof parser. PSYC is easy to render and parse yourself for
simple tasks, as long as your body does not contain "\n|\n" and your
variables do not contain newlines.
* Caveats * Caveats
In every case we'll compare performance of parsing and re-rendering In every case we'll compare performance of parsing and re-rendering
these messages, but consider also that the applicative processing these messages, but consider also that the applicative processing
of an XML DOM tree is more complicated than just accessing of an XML DOM tree is more complicated than just accessing
@ -194,10 +204,27 @@ for instance by using libpurple with XMPP and PSYC accounts.
To this purpose we first need to integrate libpsyc into libpurple. To this purpose we first need to integrate libpsyc into libpurple.
* Futures * Futures
After a month of development libpsyc is already performing pretty After a month of development libpsyc is already performing pretty
well, but we presume various optimizations, like rewriting parts well, but we presume various optimizations, like rewriting parts
in assembler, are possible. in assembler, are possible.
* Related Work
If this didn't help, you can also look into:
** Adobe AMF
** ASN.1
** BSON
** Cisco Etch
** Facebook Thrift
** Google Protocol Buffers
The drawback of these binary formats is, unlike PSYC, JSON and XML
you can't edit them manually and you can't produce valid messages
by replacing variables in a simple text template. You depend on
specialized parsers and renderers to be provided.
* Appendix * Appendix
** Tools used ** Tools used