14 December 2004

Ping Messages and development efforts

Sometimes when end-users see messages like this they wonder, is there a problem?

Actually, from the end-user's perspective this development effort is transparent. The pings go through fine.

Of course, when I see a message like this:

Feedster results:
Something went wrong - -32300 : transport error - could not open socket

...I have to admit that the 'reason for pinging again' goes out the window. There's no reason to reping when the 'reason for pinging" [make sure Feedster does a screen shot and lets the feed get incorporated into the searches] generates an error message.
Sometimes when end-users see messages like this they wonder, is there a problem?

Actually, from the end-user's perspective this development effort is transparent. The pings go through fine.

Of course, when I see a message like this:

Feedster results:
Something went wrong - -32300 : transport error - could not open socket

...I have to admit that the 'reason for pinging again' goes out the window. There's no reason to reping when the 'reason for pinging" [make sure Feedster does a screen shot and lets the feed get incorporated into the searches] generates an error message.
" />