[Seaside] [Issue 553] #isolate: broken - any updates?
aa at serendip.demon.co.uk
Tue Jul 20 09:25:16 UTC 2010
It's useful that you've specified some alternatives, thanks!
Conversely, #isolate: provides a 'one-stop' solution for Seaside users, so that's another argument in its favour.
You mentioned at CS that it's never really been an issue until now (how many people noticed that it was broken since Seaside 2.7?). But Seaside's popularity is increasing, and its use as a web framework is becoming more diverse, so there will inevitably be more grumbles about this feature...
On Tue, 20 Jul 2010 09:16:15 +0100
Julian Fitzell <jfitzell at gmail.com> wrote:
> I agree that preventing a user from processing a credit card payment
> twice or going "back" into a logged-out session are reasonable
> requirements. That's not really the question, though, because
> #isolate: is only one of a probably endless variety of possible
> solutions to that problem.
> For session logout, for example, you could simply unregister the
> session or set whatever property was holding the current user to nil.
> For the credit card case you could, for example, have a WAIsolatedTask
> that only allowed itself to be run once and put the appropriate code
> in a subclass of that. (actually... hmm.... that might be a way to
> implement #isolate:... need to look into that)
> The only reason you might need #isolate: is that you can use it to
> *implicitly* protect just *part* of a Task #go method or a callback.
> What I'm wondering is how important those two aspects of the solution
> are. If only a half dozen out of thousands of users are asking for it,
> it's hard to justify classifying it as "essential".
More information about the seaside