|
Russell Hansen
Texi pets are here!
Join date: 11 Apr 2006
Posts: 107
|
07-22-2006 17:43
I'm extracting headers from my llHTTPRequest, and occassionally I'll get the answer for the X-SecondLife-Owner-Name header as "  waiting)". Anyone else had this problem and found a way around it? Is it the script that needs time to catch up, or the SL outbound comms server? If it was the script, I could put a delay in, but if it's the comms server delay, I guess there's not much I can do about it except maybe keep requesting until I get it? |
|
Moonshine Herbst
none
Join date: 19 Jun 2004
Posts: 483
|
07-22-2006 18:51
I bet it is asset server lag.
|
|
Rifkin Habsburg
Registered User
Join date: 17 Nov 2005
Posts: 113
|
07-22-2006 20:40
I assumed it's asset server lag too, although I'd like to see an official Linden response.
I've found all the header values to be unreliable. For any HTTP call that needs those values, I have the sending object pass them as a parameter in the POST block.
_____________________
Procyon Games: makers of Can't Stop, En Garde, Take it Easy, Danger Zone and Frootcake.
|
|
Russell Hansen
Texi pets are here!
Join date: 11 Apr 2006
Posts: 107
|
07-22-2006 23:26
*sigh* I basically just want to know what object and owner is making the call, was very simple if the headers were reliable  |
|
Lex Neva
wears dorky glasses
Join date: 27 Nov 2004
Posts: 1,361
|
07-23-2006 12:19
I would expect that, at the very least, the owner key will always be there, even if the system doesn't manage to resolve it to the owner's name quickly enough. So you can probably rely on the key and do your checks based on it.
Of course, remember that anyone can spoof an HTTP request with the appropriate headers...
|