Jürgen Hofmann wrote: > > The server communication takes place via a proprietary protocol over TCP/IP. > The server basically receives commands and variables and returns variables > and messages. The somehow tricky part is, that the server is not context > free, so I have to keep some context on my side whenever communicating with > the server.
I have been known to (ab)use cocoon for similar things in my early cocoon days ;-) > My idea was to simply create a transformer, which takes the command and > variables, sends them to the server and outputs the received variables and > messages. However, I don't want to pass all the context required for correct > server communication through my transformer, because for the application > logic it's not needed. Further I need an efficient way for connection > handling; I want to stay connected to the server as long as the user does > not log-out. > If i were you i'ld have a good look at the flexibility provided by flow [1], and keep the connection logic and protocol logic independent of cocoon in normal java classes. You can use the servlet session to save the state objects. If you need user interactivity you can use a basic CForm [2] to handle this. Note that there is a bit of a learning curve to all this, but it's well worth the time ! HTH Jorg [1] http://cocoon.apache.org/2.1/userdocs/flow/index.html [2] http://cocoon.apache.org/2.1/userdocs/forms/index.html --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
