That's strange <@url> is causing a crash. Someone else might have a better suggestion but theres a program in unix OS's called wget. Id assume OS X has wget as well since it is also a unix based OS.
what it does is basicly acts as a browser in that you can give it a web page address and it will download that web page. how you use it is pretty simple: wget www.mydomain.com/mypage.html how this is useful is if there is a file on the other server that when you access it doesnt affect anything (such as a welcome page), you can wget that and see if it's successful or not which tells you if the server is up or not. lets say on this other server theres an index.html which is just a welcome page. how you would use wget to see if the other server is up or not is by making a blank folder and that folder will be your "testing grounds". then your process to check is... 1) delete index.html from the folder 2) do wget www.mydomain.com/index.html (or whatever the file is) 3) if index.html exists afterwords inside that folder, the other server is up, otherwise the other server is down. there are all sorts of options to wget to specify number of times it tries and how long the timeout is for requests, so you should be able to get it to do what you want hopefully. Hope this helps! PS we have 2 servers and use wget in windows to have each server watch eachother and then send an email when one server sees that the other one is down, wget is an awesome tool. ----- Original Message ----- From: "MJPinckard" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: "Customer Support" <[EMAIL PROTECTED]> Sent: Thursday, July 15, 2004 6:24 PM Subject: Witango-Talk: @URL request crashing Witango plugin > I incorporate content from another server, and have run into a severe > problem. > > The other server was taken down for maintenance, and whenever my site > attempts to contact it, I get a hard crash of my Witango server > (Client/Server Plug-in Error) and have to manually relaunch the Witango > server to get it to work again (even for non-related requests). > > My original thought was to test the value of the @URL and if it was > empty (e.g. the server was unavailable), eliminate that piece of > content. But with it crashing at every failed request attempt , I can't > even test and build an error trap! > > What's going on, and how can I work around this problem? Eliminating the > content from the other server (and hence the @URL call) is not an > option... I've tried restarting the machine in the hopes that it was a > temporary settings problem, but no luck there either. > > Everything works fine as long as the other server is up, but I obviously > can't guarantee 100% up time on someone else's machine. > > Mac OS X 10.3.4 > Witango 5.0.1.062 > > Maggie Pinckard > ============= > Principal Research Associate > Enduse Forecasting > Lawrence Berkeley Laboratory > [EMAIL PROTECTED] > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
