[Seaside] Seaside vs Streaming
philippe.marschall at gmail.com
Tue Aug 21 04:53:35 UTC 2007
2007/8/20, Martin Kobetic <mkobetic at cincom.com>:
> Philippe Marschall wrote:
> > The cool thing about it is that's it's a simple, portable solution
> > that works nice for simple things like WADispatcherEditor. We like
> > simple, portable solutions.
> That's certainly a worth-while goal :-). I wonder if it isn't deceivingly simple in this case though.
> Looking over the WABasicAuthentication with my ignorant eye, it seems it handles the whole auth interaction by itself.
> (seems like another violation of separation of concerns to me, but anyway).
You could probably argue the same way. You could also argue that way
for doing all the redirects in #updateRoot: (which makes it feel more
> So what happens if the HTTP server has basic authentication built in (not the case with Opentalk one yet, btw) ?
As I said, simple solution for simple problems. No intention to solve
anything anything beyond that.
> What is the interaction between the two ? I assume you can turn it off on Seaside in that case, but how does Seaside get at the auth info in that case ?
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
More information about the seaside