Amora client cannot detect server down *before* starting mode

[GoogleCodeExporter]

Amora client can detect when server is down when in 'start' mode. But the
same is not true if the client has just connected to server and has not
*yet* entered in start mode.

Trying to disconnect just don't change wallpaper to disconnect mode.

Steps
1. Connect client to server (wallpaper will change to connected mode)
2. Kill server
3. Try to disconnect the client

Probably the socket is throwing an exception and stopping the code that
changes the wallpaper to disconnected mode.

Original issue reported on code.google.com by cavalcan...@gmail.com on 29 Aug 2007 at 7:31

[GoogleCodeExporter]

Maybe this is non-related, but it also seems to do with exceptions handling.

I verified a situation where killing amorad was not detected by the client 
whilst in
'Start' mode and further tries of 'Disconnect' and 'Exit' were simply ignored 
(the
client did not get out of 'Start' mode).

Using Fedora Core 7 and the Mandriva RPM package amora-server-1.0svn-2.i586.rpm.
Client is amora-1.0-1-deps.sis.

Original comment by milton.soares.filho on 28 Feb 2008 at 2:39

[GoogleCodeExporter]

I confirm this misbehavior (its probably a regression in client code). I will 
try to
investigate it later.

Original comment by cavalcan...@gmail.com on 28 Feb 2008 at 3:05

[GoogleCodeExporter]

Original comment by cavalcan...@gmail.com on 12 Mar 2008 at 11:56

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

There is no way to amora client known if the server is down *without* sending 
any
commands.

Concerning the issue reported by Milton Soares, it was an unhandled exception. 
It is
fixed on commit r 543.

Original comment by cavalcan...@gmail.com on 14 Jul 2008 at 8:20

• Changed state: Verified