Donna Dionne wrote:
HI!
Like to find out if I can get on the mailing list and ask some
questions about the protocol.
I have both the message_template.txt and the keywords.txt, but I am
still having trouble decoding the packet. I would like to find out
how I can correlate the packet type (byte 5, 6, or 7 for high, medium,
and low packet respectively) to the definitions in
message_template.txt. For example, the packet 40 00 00 01 ff ff 00
03 is a low packet of type 00 03, but what is the definition of low
packet type 00 03 in message_template.txt? and how does the file
keyword.txt help?
Any pointers would be greatly appreciated!
Best regards,
Donna
Donna, go here: https://mail.gna.org/listinfo/libsecondlife-dev/ to
subscribe to libsecondlife-dev mailing list. That's where the reply to
your last e-mail went, I've attached it here. Also feel free to drop in
#libsl on EFNet, you can usually always catch at least one developer
hanging around.
Actually low packets have eight byte headers since the id is two bytes,
instead of one byte like the medium and high frequency headers. And just
for reference, the id is one of the fields that is in network order (big
endian). Lets say the ID was 00 01 though, that would be the first low
packet you come across in the message_template. A medium frequency
header with id 03 would be the third medium frequency packet in the
template. The packets are ordered, but the blocks and fields inside the
packets are all out of order. That's why the keywords.txt list is needed
to figure out the ordering of fields and blocks.
John Hurliman
_______________________________________________
libsecondlife-dev mailing list
libsecondlife-dev@gna.org
https://mail.gna.org/listinfo/libsecondlife-dev
http://www.libsecondlife.org/
