[sldev] Jira cleanup, giving pjira a little loving

Lawson English lenglish5 at cox.net
Sat May 17 10:27:41 PDT 2008


Matthew Dowd wrote:
>
>     > I know exactly what you mean. There is a limit on IMs where they start to cap, however I am not sure when objects begin to cap.  
>
>     From the source code it looks like an inventory offer is just a special case of IM - i.e. once your IMs are capped, objects are also capped. Certainly my impression is that capping does not distinguish between inventory offer "IMs" and normal "IMs".
>
>     Anyway I've created an entry - http://jira.secondlife.com/browse/SVC-2359 - if you know this to be a duplicate, please link it.
>
>     Also, I've created one for something else bugging me for a long time - auto-coalescing of returned objects; this seems designed to make it harder to sort out your Lost&Found folder, and offers no benefits whatsoever (coalescing itself, however, is useful) - http://jira.secondlife.com/browse/SVC-2360 - again I tried to find duplicates first....
>
>     Matthew
>

It is the same packet that is delivering group/private IM and inventory 
offers (but not local chat). However, I think unless ALL of IM is hosed 
for some reason, your inventory offers should still be getting through.

A very incomplete analysis of the IM packet is found here:

https://wiki.secondlife.com/wiki/ImprovedInstantMessage

I was filling it in as I got group IM working in the Python bot, but 
that's been on hold for quite a while now.


Lawson


More information about the SLDev mailing list