Re: [Gzz-commits] manuscripts/storm article.rst

[Alatalo Toni]

On Wed, 22 Jan 2003, Benja Fallenstein wrote:

> > +antont ponders: for files storm is ok, but how about:
> > +- irc? (latency?)
> This is only a weekness if Storm is your hammer and everything must be a
> nail. ;-)

true. i guess i was just searching for the limits - which are something to
express in the article i think.

> one Storm block per chat message. But this could be bloatful; I think I
> Storm blocks may simply not be suited to this.

ok. i wanted to know your thoughts on this.

> an issue I don't see as connected with latency. Things like the p2p/DHT
> stuff are particular implementations of Storm pools-- you do not have to
> use them with IRC if they don't work for that application.

thanks for the clarification.

> Video *is* an intended application of Storm. There could be a problem
> with streaming, though, as you could not degrade quality to compensate

yes i remembered seeing some classes for it in the docs/code. will be
interesting when we get to try it out!

> > +.. multipoint live video? (both latency and throughput demands)
> Live video would not sit well at all with Storm blocks, I should think.

ok. but, unrelated to storm (so going a bit off-topic here), there can be
other ways (modules?) to be able to deal with it in gzz then, right? not
that i desparately need that very soon though..

> from it xanalogically, though. (Video and audio, btw, is where the
> 'media sharing' of Storm really pays off: you only need to store a video
> once even if you transclude it into many different sequences-- i.e.,
> possible cuts.)

quicktime actually does this too. e.g. when you make cuts and edits from a
media file they are, by default, saved as containers with references to
the original media files (there is an option to save as a stand-alone file
too).

> - Benja

~Toni