Hi Steven,
Also, once you can call back to the element that added an AJAX-
enabled form field, this can evolve into a bidirectional
communication channel between an element and a client, not just
something for form validation. That's one thing that I think is
lacking with the DWR approach: you can only communicate with a
standalone Java object that exists in a vacuum and is
reinstantiated from scratch on each interaction, rather than with a
RIFE component that has all the context about what the user is up
to and (in the case of an embedded component) about which of
several possible instances of a given UI component the user is
manipulating.
And once you have a mechanism for communicating with an element, my
gut tells me that mixing AJAX and continuations will lead to some
very compelling design patterns. But I admit I can't picture them
clearly enough off the top of my head to write them up here.
This is a very interesting train of thought and I'm sure it's totally
possible to achieve with DWR by adding RIFE-specific creators that
inject the element instance into the Java objects it instantiates.
Copying Joe (the author of DWR) on this, maybe he has some ideas
about this.
Definitely worth exploring!
Take care,
Geert
--
Geert Bevin
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
