I’m bored, so I’m going to see if I can get round this bug. 
First step: reproduction. This is easy:
Step 2: Found the offending XML:
<member><name>name</name><value><i4>1</i4></value></member>
(“i4″ should be “string”)
Step 3: Give up because my internet connection’s dying.
Step 4: Roll out fix.
Step 5: Announce success.
Are step 4 and 5 done. If not, who can/will do it?
They are done, assuming I remembered to do so. >.>
Is the change made in libsl. If yes, can you tell me what you have changed?
I can reproduce it now, if you have one folder or object with a name containing only numeric chars it will fail.
the name of the InventorySkeletonEntry was send as an integer, but i am still interested in your solution
Did you reproduce it with AjaxLife or another libsl client?
Actually I gave up changing it in libsl – it’s tied in with the XML-RPC too tightly.
My approach basically involves passing it through a secure proxy which runs the following:
$output = preg_replace("~<member><name>name</name><value><i4>(.+?)</i4></value></member>~","<member><name>name</name><value><string>$1</string></value></member>~",$output);Not exactly elegant, but it works until LL get their login stuff fixed.
I reproduced it in another libslclient without a proxy. I just removed the folder named ’20071220′ So we both worked around it
Thank you, and keep up the good work. See you in the sl grid next year i guess
Year after next.
I did the proxy thing because asking all my users to rename their stuff has the potential to be irritating.