James Cook wrote:
Reports of bugs/exploits would be of immense value to us. I may not
be the best point of contact, though, because I have more client than
server expertise. Lemme ask around and see if one of my colleagues
wants to be the point person.
In general, expect the protocol ("the message template" we call it) to
change with each release. Sorry. Almost none of the changes will be
in the core login/object transmission parts, but our scheme isn't
flexible enough to add new fields without changing the "message
template checksum" that gets checked on each login.
We're working on more flexible messaging that should make your tasks
easy.
James
My current method of bug reporting is filing a bug in the client, and
letting llPhoenix or llKelly know in #secondlife on EFNet, referencing
the bug report name. If there is a better way for this please let us know.
Syncing to changes in the keywords list and message template (comm.dat)
has become an automated process at this point, that's not a worry. What
would be more interesting is information like "the entire way objects
are handled is being restructured right now" for example, but I think
access to the preview grids is mostly warning enough.
John
_______________________________________________
libsecondlife-dev mailing list
libsecondlife-dev@gna.org
https://mail.gna.org/listinfo/libsecondlife-dev
