[Cal]

LifeStyles has been having a lot of problems with errors, and freezing. After careful ananlysis and discussing the situation with people that have IT expertise, I decided to test palacebox, or manorbox as it is called.

The change has resulted in substantially less errors, less freezing, and the speed is significantly improved.

This gives us the capability to zero in on the Manor client without having to figure out if we have server problems or client problems. My errors since moving are as follows:

Froze when attempting to change rooms using the user list. (twice)
»: *** Error 503
(HTTP Server:
Service
Unavailable)
Downloading
----------------------
Error 403 (HTTP Server: Forbidden)
Downloading prop
-------------------------
*** Error 12017 (The
operation was
canceled, usually
because the handle on
which the request was
operating was closed
before the operation
completed)
Downloading prop
------------------------------
I hope this information helps.
_________________
Frank J Palank

[Rhonk]

All of the errors except 12017 are specific to the webserver. With the exception of 12017, the definitions are as follows:

Error Code 403 is for a forbidden resource. This means the prop might have the wrong permissions or the webserver might be restricting the certain file. I would contact the host about this issue if it persists. If the host believes the permissions to be set incorrectly by the manor daemon then I'm sure Scots will resolve it. I ran into this problem way back when and it's a simple fix of using the chmod command a few times.

Error Code 503 is for a lack of system resources on the webserver. For example, if a server is overloaded it will send header to the client with the error code and sometimes a small text only page to cut down on resources. If this is on a popular, high profile server this wouldn't be uncommon.

However, better error handling would be useful in the client. For web browser it just takes the error, grabs the page, and displays it. I'm not sure what Manor does but my suggestion would be to take the error, dump the page, and display an error in the log.

Since 2/3 of these errors pertain to the webserver I would recommend talking to you host about it first. And my suggestion for Scots is to see about implementing better error handling for webservers. The only problem with this is the majority of the web uses Apache but what will happen to my Roxen server? My Caudium server? Etc? The answer to that is since it has a small market share to disregard it as it is not standards compliant. I'm a firm believer in "You don't support documented standards why should we support you."
_________________
-Erik "Rhonk" Arnson

[Scotsman]

Actually Rhonk, the 403 has to do with timing and the way the manor server interacts with the webserver. I'm working on a fix for it now.

I have a fix for the 503 error in work now. Basiclly making sure the client retry's after a delay when it gets one.