Eelco Hillenius schrieb:
I can't speak for Igor - though we have talked about that too - but
for my opion see e.g.
http://www.theserverside.com/news/thread.tss?thread_id=39579#204913
Thanks for the link.
mind you that Wicket allows for very fancy state optimizations as
well.
Quoting from a response from Bruce Tate (taken from your link):
| check out Seaside's online store as an example of a wizard with
| continuations. It's a classic shopping cart. The code:
|
| go
| | shipping billing creditCard |
| cart _ WAStoreCart new.
| self isolate:
| [[self fillCart.
| self confirmContentsOfCart]
| whileFalse].
|
| self isolate:
| [shipping <- self getShippingAddress.
| billing <- (self useAsBillingAddress: shipping)
| ifFalse: [self getBillingAddress]
| ifTrue: [shipping].
| creditCard <- self getPaymentInfo.
| self shipTo: shipping billTo: billing payWith: creditCard].
|
| self displayConfirmation.
I like this a lot better than spreading the logic over several
components and handlers.
So, I'm not pro continuations in Wicket at this point, except for the
ajax optimization with Jetty, which will probably be implemented
transparently.
I am not asking you to write it :) I just want to discuss the idea,
because I would like to know what benefit or problems/incompatibilities
other people see.
Geert has done the extra effort
of ensuring his continutation API can be used without RIFE
WebWork already has some support.
Timo
, so that's
certainly an option (I think, because I never seriously thought about
how this would/ should be integrated in Wicket).
My 2c,
Eelco
On 4/14/06, Timo Stamm <[EMAIL PROTECTED]> wrote:
Igor,
do you know RIFE/Continuations? It uses continuations for better state
handling and control flow instead of better performance.
There are some examples in this slide (pages 5 to 8):
https://www.dev.java.net/files/documents/204/3120/rife_fosdem_2004.pdf
It really looks like an interesting concept. You could keep complicated
flow control for business-logic at one place.
It changes the bytecode using ASM, but if it's done properly, I don't care.
Timo
Igor Vaynberg schrieb:
well, at some point the server calls will start returning right? and so
xmlhttprequest objects will start being reused. it will consume memory to a
certain point and then stop. if you ask me 100ms for an ajax update is
unreasonable anyways, this is what jetty 6 continuations are for which would
be relatively simple to integrate into wicket as an alternative for ajax
self updating behaviors.
-Igor
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
