Yes, and that's exactly what I'm imagining is a state-machine driven boot sequence. You can watch the server proceed serially through all the LayerData types from 1 to 55, sometimes doing nothing at a particular type and moving quickly onto the next and sometimes dropping off some ObjectUpdates, ImageDatas, AgentAnimations and so forth at a particular level.
I was imagining that the client was following along in synchrony and would stop at a level (by not ACKing) to make additional requests at that level. This is the state machine that my addled mind's eye was trying to see in the fog. Cheers, Scott > What is your definition of idle? At that point the server would be > sending the client LayerData packets to describe the terrain/wind/clouds > and ObjectUpdate + other object packets to describe the surrounding > world, along with handling any requests from the client for more data. I > guess I'm not following what you are trying to find? > _______________________________________________ > Libsecondlife-dev mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/libsecondlife-dev > _______________________________________________ Libsecondlife-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/libsecondlife-dev
