Protocol Transport Layer Comparison

[Tommi Laukkanen]

Hi

Here is a transport layer comparison of VW protocols.

http://www.bubblecloud.org/wiki/-/wiki/Main/Comparison

SLUDP is still missing and any help with that would be appreciated.

regards,
Tommi

[Tommi Laukkanen]

This thread is continuation from rex list threads:

http://groups.google.com/group/realxtend-dev/browse_thread/thread/f5a1afd52bea264d
http://groups.google.com/group/realxtend-dev/browse_thread/thread/8fe0f7e8a5d9611b

[Tommi Laukkanen]

> Yes. SLUDP has a message ID field for each message. A few years ago when
> the RealXtend project was in its inception, we extended our own messages
> using unused message IDs. However, due to practical difficulties with the
> protocol libraries, some of these extensions were later on scrapped, and
> we stopped adding new messages this way. SLUDP also has a single message
> called GenericMessage, inside which you can serialize whatever you want.
> Each GenericMessage has an ascii string to identify what the message
> actually is, and RealXtend uses custom application messages based on this
> structure.
>
> The specifics can be seen herehttp://wiki.secondlife.com/wiki/GenericMessage. As one can see,
> serializing a whole message protocol inside this is very ineffective.

So it can be used with custom message layer and only disadvantage is
that you will be carrying the unused SLUDP message layer
implementation in your distribution. If I remember correctly it is
currently packaged as one dll. Good enough to get the mark in the
matrix but maybe a bit sub optimal especially if there is no clean API
to be used without SLUDP message dependencies.

-tommi