Small poller patch

[Red Squirrel]

I have applied a patch to the poller which will allow it to work with older versions of sphere.  In the older version it does not send a 0x0 at the end of the string and the poller would just time out on that, now it does time out, because there is no set way to know when to stop reading, but it does not ignore the data, instead of looks for the data it needs anyway and uses it if it's there.  This will also increase compatibility with any other server that does not send  a 0x0.  now, as long as clients=[number] exists somewhere in the response it should take it.

Keep in mind that if there is no 0x0 at the end of the string, the "ping" will be very high, because of the way it is calculated.  I may change/remove the ping feature in the future.

Archived topic from UOG, old topic ID:58, old post ID:143

[Red Squirrel]

Oh and the list may look a bit wacky for a bit, and don't mind the fact that it says 500+ shards.  What I did is I set all shards as active so that the poller can rerun them all as the new poller may be able to gather info from ones it was not able to before.  That means that any existing shard that went inactive should go active if it's online now.

I expect this to take several days before things fix themselves, as lot of those are really offline, and those are the ones that take the longest to poll as it has to wait for the connectivity time out, and retries several times.  I'll have to selectively go and set those ones back as inactive.

The new poller that is not ready yet will address this issue as it is multi threaded.

Archived topic from UOG, old topic ID:58, old post ID:144

[Red Squirrel]

Seems like everything fixed itself already, all good now! 

Archived topic from UOG, old topic ID:58, old post ID:145