One big problem with this below:If you want to do that call (send and wait) in a Form.onSubmit or Link.onClick We already have to be in a seperate thread.So that would mean that the user has to specify it somehow that when a request comes in for something
that we start that in a seperate thread.I
Johan Compagner wrote:
ahh so a program on the webserver just runs in its own thread. (every
session has its own thread)
And the webserver threads are dispatchting to those threads and then getting
response from them.
That doesn't look to hard to do. (the burden on the webserver would improved
ahh so a program on the webserver just runs in its own thread. (every session has its own thread)And the webserver threads are dispatchting to those threads and then getting response from them.That doesn't look to hard to do. (the burden on the webserver would improved greatly)
If we build
That was the point I was trying to make. The point of
onSubmit/onClick handlers on each component is moot because you are
already within the method which is going to do the processing.
I'm not sure if event handlers on a page would solve the issue
either. What happens when you have multiple
Boy oh boy! I want this under Wicket:
http://weblogs.java.net/blog/navaneeth/archive/2005/11/_one_interestin.html
I leave it up to you guys to figure out the details ;)
Gili
--
http://www.desktopbeautifier.com/
---
This SF.net
I don't think continuations would fit at all in Wicket.
Components and continuations just don't seem to me that they would mesh
at all. The problem is that a form component, for example,
contains the logic for submission and you must build and add it to the
page before the control is sent to the
Actually, instead of just looking at the name, continuations, you
should look at want you want to acchieve. And then the large thing
with continuations would be that you could do:
... init components ...
... render page ...
... getUserInput and do something with it ...
... processAndWait ...
