After what I understand, you want to have a server process that
communicate with other servers on other machines. And sometimes,
someone uses the web interface to configure your server. The main
business lies in in the server process. Is it right ?
I think it could be more interesting to see the server process and the
web interface as two separate pieces : that will make the server
independant of the web interface. So if you want to upgrade the web
tier, you won't have to restart the server process doing the important
work. You can even imagine having your server process and your web tier
hosted on different machines.
Your web tier can then communicate only with the data store or with your
server process through web services or another protocol like JMS
(depends on your needs).
Antoine
Troy Cauble a écrit :
Wicket is my first exposure to web server programming. I don't have the
usual background in spring, hibernate, tomcat, jetty, or even maven.
The Wicket I've written is for the configuration of a distributed application.
Now I need server functionality that, based on this configuration data,
will communicate with clients and other servers, do scheduling, etc.
Can/should this server live within my Wicket app, perhaps started
by creating threads in my WebApplication's constructor or init() ??
Or should this server live in a separate process and only communicate
with the configuration data store?
Thanks,
-troy
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
