Just remember that using reflection won't automatically make all of the
manual packet handling go away. Two example are ParcelOverlay, which
comes in four separate packets and has to be reassembled in to a single
byte array, and almost anything with a Data field that is the LL way of
doing polymorphic fields. MultipleObjectUpdate is a good example of this.
It will (if I understand correctly) remove all the repetitive work of
disassembling incoming packets though. We already have a system in place
where each packet has a name and full structure and type information;
leveraging C# abilities with this information is the next logical step.
I'm still wondering if anonymous types could be used for the dynamic
class generation though, or are they not suited for the task?
John
_______________________________________________
libsecondlife-dev mailing list
libsecondlife-dev@gna.org
https://mail.gna.org/listinfo/libsecondlife-dev
