Second Life Forums Archive - X-SecondLife-Owner-Name = (waiting) ???

Yo Brewster

Registered User

Join date: 1 Feb 2006

Posts: 139

09-02-2007 13:10

In one of the gadgets I've created, I'm doing an llHTTPRequest and I capture the name of the person who is actually wearing the gadget when it posts the info to my server. In 80% of the cases, the header variable X-SecondLife-Owner-Name will contain the correct SL Name but from time to time the SL Name will come through as "

waiting)". Does anybody have any idea why this would happen? I assumed it was a SL fluke but it seems that the (waiting) text seems to be consistent for certain ppl.

Thanks!
Yo

_____________________

Damet Neumann

Registered User

Join date: 21 Apr 2006

Posts: 140

09-02-2007 15:52

i believe it to be a database issue within s/l
if you look sometimes land says waiting instead of who owns it and items say waiting instead of who owns them i see it alot on the weekends

Animations Pfeffer

Registered User

Join date: 29 Jul 2007

Posts: 99

09-02-2007 16:01

You can use a timer, and if the owner is (waiting) then try to get the owner later.

Keiki Lemieux

I make HUDDLES

Join date: 8 Jul 2005

Posts: 1,490

09-02-2007 17:26

Wait until you see (hippos).

_____________________

imakehuddles.com/wordpress/

Malachi Petunia

Gentle Miscreant

Join date: 21 Sep 2003

Posts: 3,414

09-02-2007 17:33

From: someone

Wait until you see (hippos).

Surprisingly, that isn't a joke. If you test the return string check for "

waiting)" and "

hippos)".

_____________________

Yo Brewster

Registered User

Join date: 1 Feb 2006

Posts: 139

09-02-2007 18:53

From: Animations Pfeffer

You can use a timer, and if the owner is (waiting) then try to get the owner later.

You can't use a timer since this information is passed to a web server by using the http command. The strange thing is that this only seems to happen consistently to some users and not to others.

_____________________

Kenn Nilsson

AeonVox

Join date: 24 May 2005

Posts: 897

09-03-2007 08:54

I've been dealing with this issue for quite a while--and yes, there's both (waiting) and (hippos). It does happen consistently with some avatars, and not with others. Additionally, the avatars it happens consistently with--in my experience--tend to be the same people who consistently have issues with SL.

I had theorized that the event occurred when avatars were logging in and the http was sent too quickly during their load-up phase. Such is not the case, but I continue to hold the theory that it's part of a load-up phase communication between server and client that occurs during either login or region-change. My theory is that slower connections/less capable computers engage in a slower communication and that a script asking for information right away may achieve an answer before the information for it is available...

...of course there is all sorts of room for holes in my theory...but as a guy who's been dealing with this issue for 6+ months I can tell you that:

a) It does not happen consistently and the (waiting) / (hippos) only occurs with avatar name, not with UUID. Therefore, if your item sends info to its web database more than once, you can eventually override all (waiting) and (hippos) entries with names (just make sure they don't override in reverse).

b) It appears to only happen with people who consistently have problems with SL and lag. My theory is not that SL has a rogue asset-server, but rather that these people have slower connections / older computers.

_____________________

--AeonVox--

Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms chasing ghosts, eating magic pills, and listening to repetitive, addictive, electronic music.

Yo Brewster

Registered User

Join date: 1 Feb 2006

Posts: 139

09-03-2007 11:26

From: Kenn Nilsson

I've been dealing with this issue for quite a while--and yes, there's both (waiting) and (hippos). It does happen consistently with some avatars, and not with others. Additionally, the avatars it happens consistently with--in my experience--tend to be the same people who consistently have issues with SL.

I had theorized that the event occurred when avatars were logging in and the http was sent too quickly during their load-up phase. Such is not the case, but I continue to hold the theory that it's part of a load-up phase communication between server and client that occurs during either login or region-change. My theory is that slower connections/less capable computers engage in a slower communication and that a script asking for information right away may achieve an answer before the information for it is available...

...of course there is all sorts of room for holes in my theory...but as a guy who's been dealing with this issue for 6+ months I can tell you that:

a) It does not happen consistently and the (waiting) / (hippos) only occurs with avatar name, not with UUID. Therefore, if your item sends info to its web database more than once, you can eventually override all (waiting) and (hippos) entries with names (just make sure they don't override in reverse).

b) It appears to only happen with people who consistently have problems with SL and lag. My theory is not that SL has a rogue asset-server, but rather that these people have slower connections / older computers.

I guess the solution would be to always pass the second life name along with the http request and if (waiting) or (hippos) (???) is detected, simply use the query string var instead of the header variable. I just adjusted all my scripts so I guess I'm fine now. Thank you for your very valuable input - I was just making sure I wasn't becoming insane

_____________________

Animations Pfeffer

Registered User

Join date: 29 Jul 2007

Posts: 99

09-03-2007 20:57

From: Yo Brewster

You can't use a timer since this information is passed to a web server by using the http command. The strange thing is that this only seems to happen consistently to some users and not to others.

Use the timer BEFORE passing it to the server.

Lets say you call the timer and get the owner inside the timer function. If owner != (wait) then pass to the server, if not, call again the timer.

Should work.

Dire Graves

Registered User

Join date: 3 Sep 2007

Posts: 51

09-04-2007 21:08

From: Kenn Nilsson

I've been dealing with this issue for quite a while--and yes, there's both (waiting) and (hippos). It does happen consistently with some avatars, and not with others. Additionally, the avatars it happens consistently with--in my experience--tend to be the same people who consistently have issues with SL.

I had theorized that the event occurred when avatars were logging in and the http was sent too quickly during their load-up phase. Such is not the case, but I continue to hold the theory that it's part of a load-up phase communication between server and client that occurs during either login or region-change. My theory is that slower connections/less capable computers engage in a slower communication and that a script asking for information right away may achieve an answer before the information for it is available...

...of course there is all sorts of room for holes in my theory...but as a guy who's been dealing with this issue for 6+ months I can tell you that:

a) It does not happen consistently and the (waiting) / (hippos) only occurs with avatar name, not with UUID. Therefore, if your item sends info to its web database more than once, you can eventually override all (waiting) and (hippos) entries with names (just make sure they don't override in reverse).

b) It appears to only happen with people who consistently have problems with SL and lag. My theory is not that SL has a rogue asset-server, but rather that these people have slower connections / older computers.

That makes sense. I have a friend who is always (waiting) and that girl is running 3 copies of SL on the same connection. I'm sure that slows her down quite a bit.

X-SecondLife-Owner-Name = (waiting) ???
Yo Brewster Registered User Join date: 1 Feb 2006 Posts: 139	09-02-2007 13:10 In one of the gadgets I've created, I'm doing an llHTTPRequest and I capture the name of the person who is actually wearing the gadget when it posts the info to my server. In 80% of the cases, the header variable X-SecondLife-Owner-Name will contain the correct SL Name but from time to time the SL Name will come through as "waiting)". Does anybody have any idea why this would happen? I assumed it was a SL fluke but it seems that the (waiting) text seems to be consistent for certain ppl. Thanks! Yo _____________________
Damet Neumann Registered User Join date: 21 Apr 2006 Posts: 140	09-02-2007 15:52 i believe it to be a database issue within s/l if you look sometimes land says waiting instead of who owns it and items say waiting instead of who owns them i see it alot on the weekends
Animations Pfeffer Registered User Join date: 29 Jul 2007 Posts: 99	09-02-2007 16:01 You can use a timer, and if the owner is (waiting) then try to get the owner later.
Keiki Lemieux I make HUDDLES Join date: 8 Jul 2005 Posts: 1,490	09-02-2007 17:26 Wait until you see (hippos). _____________________ imakehuddles.com/wordpress/
Malachi Petunia Gentle Miscreant Join date: 21 Sep 2003 Posts: 3,414	09-02-2007 17:33 From: someone Wait until you see (hippos). Surprisingly, that isn't a joke. If you test the return string check for "waiting)" and "hippos)". _____________________
Yo Brewster Registered User Join date: 1 Feb 2006 Posts: 139	09-02-2007 18:53 From: Animations Pfeffer You can use a timer, and if the owner is (waiting) then try to get the owner later. You can't use a timer since this information is passed to a web server by using the http command. The strange thing is that this only seems to happen consistently to some users and not to others. _____________________
Kenn Nilsson AeonVox Join date: 24 May 2005 Posts: 897	09-03-2007 08:54 I've been dealing with this issue for quite a while--and yes, there's both (waiting) and (hippos). It does happen consistently with some avatars, and not with others. Additionally, the avatars it happens consistently with--in my experience--tend to be the same people who consistently have issues with SL. I had theorized that the event occurred when avatars were logging in and the http was sent too quickly during their load-up phase. Such is not the case, but I continue to hold the theory that it's part of a load-up phase communication between server and client that occurs during either login or region-change. My theory is that slower connections/less capable computers engage in a slower communication and that a script asking for information right away may achieve an answer before the information for it is available... ...of course there is all sorts of room for holes in my theory...but as a guy who's been dealing with this issue for 6+ months I can tell you that: a) It does not happen consistently and the (waiting) / (hippos) only occurs with avatar name, not with UUID. Therefore, if your item sends info to its web database more than once, you can eventually override all (waiting) and (hippos) entries with names (just make sure they don't override in reverse). b) It appears to only happen with people who consistently have problems with SL and lag. My theory is not that SL has a rogue asset-server, but rather that these people have slower connections / older computers. _____________________ --AeonVox-- Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms chasing ghosts, eating magic pills, and listening to repetitive, addictive, electronic music.
Yo Brewster Registered User Join date: 1 Feb 2006 Posts: 139	09-03-2007 11:26 From: Kenn Nilsson I've been dealing with this issue for quite a while--and yes, there's both (waiting) and (hippos). It does happen consistently with some avatars, and not with others. Additionally, the avatars it happens consistently with--in my experience--tend to be the same people who consistently have issues with SL. I had theorized that the event occurred when avatars were logging in and the http was sent too quickly during their load-up phase. Such is not the case, but I continue to hold the theory that it's part of a load-up phase communication between server and client that occurs during either login or region-change. My theory is that slower connections/less capable computers engage in a slower communication and that a script asking for information right away may achieve an answer before the information for it is available... ...of course there is all sorts of room for holes in my theory...but as a guy who's been dealing with this issue for 6+ months I can tell you that: a) It does not happen consistently and the (waiting) / (hippos) only occurs with avatar name, not with UUID. Therefore, if your item sends info to its web database more than once, you can eventually override all (waiting) and (hippos) entries with names (just make sure they don't override in reverse). b) It appears to only happen with people who consistently have problems with SL and lag. My theory is not that SL has a rogue asset-server, but rather that these people have slower connections / older computers. I guess the solution would be to always pass the second life name along with the http request and if (waiting) or (hippos) (???) is detected, simply use the query string var instead of the header variable. I just adjusted all my scripts so I guess I'm fine now. Thank you for your very valuable input - I was just making sure I wasn't becoming insane _____________________
Animations Pfeffer Registered User Join date: 29 Jul 2007 Posts: 99	09-03-2007 20:57 From: Yo Brewster You can't use a timer since this information is passed to a web server by using the http command. The strange thing is that this only seems to happen consistently to some users and not to others. Use the timer BEFORE passing it to the server. Lets say you call the timer and get the owner inside the timer function. If owner != (wait) then pass to the server, if not, call again the timer. Should work.
Dire Graves Registered User Join date: 3 Sep 2007 Posts: 51	09-04-2007 21:08 From: Kenn Nilsson I've been dealing with this issue for quite a while--and yes, there's both (waiting) and (hippos). It does happen consistently with some avatars, and not with others. Additionally, the avatars it happens consistently with--in my experience--tend to be the same people who consistently have issues with SL. I had theorized that the event occurred when avatars were logging in and the http was sent too quickly during their load-up phase. Such is not the case, but I continue to hold the theory that it's part of a load-up phase communication between server and client that occurs during either login or region-change. My theory is that slower connections/less capable computers engage in a slower communication and that a script asking for information right away may achieve an answer before the information for it is available... ...of course there is all sorts of room for holes in my theory...but as a guy who's been dealing with this issue for 6+ months I can tell you that: a) It does not happen consistently and the (waiting) / (hippos) only occurs with avatar name, not with UUID. Therefore, if your item sends info to its web database more than once, you can eventually override all (waiting) and (hippos) entries with names (just make sure they don't override in reverse). b) It appears to only happen with people who consistently have problems with SL and lag. My theory is not that SL has a rogue asset-server, but rather that these people have slower connections / older computers. That makes sense. I have a friend who is always (waiting) and that girl is running 3 copies of SL on the same connection. I'm sure that slows her down quite a bit.

Welcome to the Second Life Forums Archive

X-SecondLife-Owner-Name = (waiting) ???