psyc-mirrors
/
libpsyc
mirror of git://git.psyc.eu/libpsyc
1
0
Fork 0
Code Issues Releases Wiki Activity

xml-unfriendly complete

This commit is contained in:
psyc://psyced.org/~lynX 2011-05-23 16:08:26 +02:00
parent 6898cc65e4
commit c705ba2259
6 changed files with 33 additions and 35 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
bench/benchmark.org
View File

@ -37,6 +37,8 @@ Same test with characters which aren't practical
in the XML syntax.
#+INCLUDE: packets/xml-unfriendly.xml src xml
#+INCLUDE: packets/xml-unfriendly.json src js
#+INCLUDE: packets/xml-unfriendly.psyc src psyc
** A message with PSYC-unfriendly strings
PSYC prefixes data with length as soon as it
@ -93,16 +95,8 @@ np
** An average chat message
XMPP:
#+INCLUDE: packets/chat_msg.xml src xml
JSON:
#+INCLUDE: packets/chat_msg.json src js
PSYC:
#+INCLUDE: packets/chat_msg.psyc src psyc
Why PSYC doesn't have an id? Because packet counting from contexts
@ -155,7 +149,19 @@ Pure syntax comparisons above, protocol performance comparisons below:
These tests were performed on a 2.53 GHz Intel(R) Core(TM)2 Duo P9500 CPU.
* Conclusions
... TBD ...
The Internet has developed two major breeds of protocol formats.
The binary ones are extremely efficient but usually not very flexible
while the plain-text ones are reaching out for achieving perfection
in data representation while leaving the path of efficiency. Some
protocols such as HTTP and SIP are in-between these two schools,
offering both a text-based extensible syntax (it's actually easier to
add a header to HTTP than to come up with a namespace for XMPP...)
and the ability to deliver binary data. But these protocols do not
come with native data structure support. PSYC is a protocol that
combines the compactness and efficiency of binary protocols with the
extensibility of text-based protocols and still provides for enough
data structuring to rarely require the use of other data formats.
* Criticism
Are we comparing apples and oranges? Yes and no, depends on what you
@ -192,7 +198,6 @@ After a month of development libpsyc is already performing pretty
well, but we presume various optimizations, like rewriting parts
in assembler, are possible.
* Appendix
** Tools used
@ -208,3 +213,5 @@ xmlbench:
: parse/libxml-sax 1000000 $file
: parse/libxml 1000000 $file
: parse/rapidxml 1000000 $file
See also "make bench"

9
bench/packets/json-unfriendly.xml
View File

@ -1,10 +1,5 @@
<message
from='romeo@example.net/orchard'
id='sl3nx51f'
to='juliet@example.com/balcony'
type='chat'
xml:lang='en'>
<body>"Neither, fair saint, if either thee dislike.", he said.
<message from='romeo@example.net/orchard' to='juliet@example.com/balcony'>
<body>"Neither, fair saint, if either thee dislike.", he said.
And
the
rest

11
bench/packets/psyc-unfriendly.xml
View File

@ -1,12 +1,7 @@
<message
from='juliet@example.com/balcony'
id='c8xg3nf8'
to='romeo@example.net'
type='chat'
xml:lang='en'>
<subject>I implore you with a pointless
<message from='juliet@example.com/balcony' to='romeo@example.net'>
<subject>I implore you with a pointless
newline in a header variable</subject>
<body>Wherefore art thou, Romeo?
<body>Wherefore art thou, Romeo?
|
And for practicing purposes we added a PSYC packet delimiter.</body>
</message>

3
bench/packets/xml-unfriendly.json Normal file
View File

@ -0,0 +1,3 @@
["message",{"from":"juliet@example.com/balcony","to":"romeo@example.net"},
"Pro\x010De\x017D jsi ty, Romeo?"]

6
bench/packets/xml-unfriendly.psyc Normal file
View File

@ -0,0 +1,6 @@
:_source psyc://example.com/~juliet
:_target psyc://example.net/~romeo
_message
Pro&#x010D;e&#x017D; jsi ty, Romeo?
|

12
bench/packets/xml-unfriendly.xml
View File

@ -1,11 +1,3 @@
<message
from='juliet@example.com/balcony'
id='z94nb37h'
to='romeo@example.net'
type='chat'
xml:lang='en'>
<body>Wherefore art thou, Romeo?</body>
<body xml:lang='cs'>
Pro&#x010D;e&#x017D; jsi ty, Romeo?
</body>
<message from='juliet@example.com/balcony' to='romeo@example.net'>
<body>Pro&#x010D;e&#x017D; jsi ty, Romeo?</body>
</message>