[Seaside] Seaside vs Streaming

Conrad Taylor conradwt at gmail.com
Mon Aug 20 21:26:11 UTC 2007

Hi Martin, I feel the same about this issue.  Thus, I was wondering, if I
was building an application like YouTube.com is Seaside, what approach one
would use?  YouTube.com is a extreme example due to the amount of traffic,
uploads, and downloads.  Hence, I would like to understand it's architecture
for streaming here in a small and simple that can easily scale by adding
more VM or other techniques and technologies.

On 8/20/07, Martin Kobetic <mkobetic at cincom.com> wrote:
> >
> > But if the session made a pass over the component tree for each phase,
> > these problems could be easily overcome. Redirects or 401 status codes
> > could be set in the headers pass instead of during rendering, and so no
> > big structural changes would be needed.
> >
> > I'm assuming here that there is some desire to have Seaside do
> > streaming, or why would we have the discussion? If we don't make the
> > necessary changes for all Seaside features to work with streaming
> > responses, then we may as well not bother trying to support it at all.
> > If it's reserved for a special optimization case, then it will never get
> > used anyway.
> My understanding is, that some of the new hip and cool web programming
> techniques require the streaming hookup. So presumably the decision is: do
> we want Seaside to support those or not. The HTTP server can handle direct
> streaming of files (in both directions) without explicit streaming support
> in Seaside (if we avoid defeating it with things like WAFile>>contents). So
> it's not about handling large files. It's about being able to do new kinds
> of web programming. Assuming the decision is yes, we want streaming, then
> being able to either stream or not for any particular response should yield
> the best of both, and should suite most purposes. So I'm not sure what
> exactly is the argument here. Does the streaming hookup proposed here seem
> too complicated, compared to the benefits?
> Martin
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20070820/62bda87f/attachment-0001.htm

More information about the seaside mailing list