I was unclear. I was thinking of the transition between the initial cache update & priming phase and steady state message shuffling. I've noticed that the server seems to idle by sending the client StartPingChecks to let the client digest what it has been sent and ask for anything additional it thinks it could use. The transition seems to be when 1) the client's CompletePingCheck is up-to-date, 2) the client isn't making any more requests and 3) the server has no additional precache information to send. Now we're at a quiescent steady state and the games can begin.
> [EMAIL PROTECTED] wrote: > >> For example, as a very basic question, how does the client know that the >> server is done sending it cache information so that it can finish >> digesting what it has and turn control over to the user? >> > > The server is never done sending information, it's constantly streamed > for the entire connection. The turning point in the official client > appears to be when the clothing assets have finished downloading and the > appearance is sent back to the server. There's nothing fundamentally > stopping you from moving around and doing things before that, but SL is > less enjoyable if you can't see your avatar. > > John > _______________________________________________ > 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
