> > For regular posts, there is a way out of this: stateless pages with > > stateless forms. For Ajax calls there isn't currently. I'm still > > advocating that, but we're not sure how that would work best yet. > > Concrete ideas are welcome. Johan, maybe you could state your > > objections or difficulties with that here so that we can discuss > > further? > > > I think generating such a hybrid url can be done just fine. > I just thing that is it for ajax not really needed, Because with ajax you > get some new data for specific components or replace a part in the page. > But if the page is constantly created. Then the page where you talk to > could be completely changed. For example if you have a listview/repeater > in the page then that one if you generate it again without rerendering the > complete > page in the browser you are from that point on completely out of sync. > So ajax request that are then still on the page don't work anymore.
I think there are plenty of use cases for stateless Ajax behaviors - stock tickers, chat apps, etc - but the big question is whether it would be smart to implement them as component bound behaviors in the first place. Maybe it makes more sense to have a pattern more like shared resources for that. Maybe some pattern that would work with a very dumbed down version of AjaxRequestTarget, e.g. without the functionality to re-render components etc, together with something that works like ResourceReference to enable users to let components reference such a service. Eelco ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
