IMHO, I believe that JAMES should have an actual GUI interface for
management in addition to any command line management interface. This will
help in the overall acceptance of JAMES as an alternative to other mail
servers.
So here are some questions:
1.) Should the server be able to be run in GUI mode which will provide an
always on GUI? This could be activated by a switch on the command line.
2.) Should administration be done remotely, and if so over which protocol
(RMI, CORBA, HTTP, etc.)?
3.) Will JAMES need to be modified extensively to support a GUI management
interface?
4.) How does Avalon fit in? (i.e. should a management UI be able to modify
the config docs?)
Any other thoughts and answers to this question are appreciated.
Sincerely,
Anthony Eden
----------
>From: "Eric Hancock" <[EMAIL PROTECTED]>
>To: "Java Apache Mail Server" <[EMAIL PROTECTED]>
>Subject: Re: How to properly shutdown the JAMES?
>Date: Wed, Jun 21, 2000, 4:51 PM
>
>
> Right, but any product you roll out to a production environment needs some
> kind of management interface. Not necessarily a UI, but hooks to get
> information at runtime, and to shut down / take a server offline.
>
> I could help with this if people think it would be useful.
>
> E -
>
>> Just kill the process... shouldn't hurt anything (we hope).
>>
>> "Muly, VerySafe" wrote:
>>>
>>> Hi
>>>
>>> Is there is a correct way to tell JAMES to shutdown or restart without
>>> killing the proccess?
>>>
>>> Regards,
>>>
>>> Muly.
>
>
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://java.apache.org/>
> Problems?: [EMAIL PROTECTED]
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/>
Problems?: [EMAIL PROTECTED]
