diff options
| author | Justin Clark-Casey (justincc) | 2010-12-02 01:55:49 +0000 |
|---|---|---|
| committer | Justin Clark-Casey (justincc) | 2010-12-02 02:01:01 +0000 |
| commit | 5246d98b8df3cc613a199851c3ac33ec753f522a (patch) | |
| tree | d4ce71333504fef05419ba27cbfbeabcaad0f4c1 /bin/libopenjpeg-dotnet-2.1.3.0-dotnet-1-i686.so | |
| parent | minor: add some method doc (diff) | |
| download | opensim-SC_OLD-5246d98b8df3cc613a199851c3ac33ec753f522a.zip opensim-SC_OLD-5246d98b8df3cc613a199851c3ac33ec753f522a.tar.gz opensim-SC_OLD-5246d98b8df3cc613a199851c3ac33ec753f522a.tar.bz2 opensim-SC_OLD-5246d98b8df3cc613a199851c3ac33ec753f522a.tar.xz | |
Stop LLUDPServer sending updates after object deletes by always queueing deletes
If an LL 1.23.5 client (and possibly earlier and later) receives an object update after a kill object packet, it leaves the deleted prim in the scene until client relog
This is possible in LLUDPServer if an object update packet is queued but a kill packet sent immediately.
Beyond invasive tracking of kill sending, most expedient solution is to always queue kills, so that they always arrive after updates.
In tests, this doesn't appear to affect performance.
There is probably still an issue present where an update packet might not be acked and then resent after the kill packet.
Diffstat (limited to 'bin/libopenjpeg-dotnet-2.1.3.0-dotnet-1-i686.so')
0 files changed, 0 insertions, 0 deletions