> mhmm, now I got it... > In other frameworks and also in Wicket it's common to use GET request for > doing some action on the server ( for example Link#onClick(...) ), so it's > generally useful concept. I didn't see it from this point of view before.
Yeah. Like I said, officially GET requests should be idempotent. And that's fine when you talk about documents but hardly makes sense when you think about applications. Even if you avoid state changing things like deleting records with links, you still have to deal with things like data that might get stale between requests. So personally, I think the idea of having idompotent web requests as part of user interfaces is flawed to start with. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
