On 4/13/07, Andreas Pardeike <[EMAIL PROTECTED]> wrote:
Forgive me if the following is wrong, but isn't it possible to have something like an edit context as in WebObjects that will not accept a second request with the same edit context ID? If one would keep track of requests to the server with a sequence id, it would be possible to process any request with an already handled id in a way that would ignore it and process it as a simple refresh of the page? I have a good friend in Germany who is now the mastermind behind Project Wonder which is the extension framework for WebObjects. Naturally, he's a WebObjects guru and usually points out the advantages of it compared with Tapestry. From what he tells me (and with the limited ability of me to digest it) I think that they use redirect-after-post only sporadic.
Really i don't know nothing about WebObjects, said that, what you're talking about seems a neat features indeed. -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
