[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [corona-dev] Corona Server Shutdown
|
When the Corona server is being shutdown, it will post a container
shutdown event to every open ContextContainer.
Q: How should each Corona Workbench client handle the container
shutdown event?
* How should the user be notified?
Maybe containers should be decorated with offline icon. Some
disconnected plugs. We could also show an dialog box with message that
server was shut down, but with an option that the message box doesn't
display any more.
* Should the WB client be able to continue using the container
offline?
I think finally we want to allow users work offline. So he should be
able to continue an offline work.
* Should the WB client periodically attempt to reconnect to the
server?
I think so. Probably server won't be able to notify in any way that it
is up again.
I think that shudown event should contain a time and date before which
clients shouldn't try to reconnect. Usually, when server goes into
maintenance, administrators can predict that it will take an hour or two.
Marcin
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
