NetScape standards, 2.0 features, and purple pages

[Wolfgang Roeckelein]

Holger Hoffstaette wrote:
> Wolfgang wrote:
> > > Netsurfer already does inline video. :-) However, that still doesn't
> > > solve
> >
> > But only MPEG, or have I missed something?
>
> Only QuickTime in various codecs and MPEG not at all. NEXTIME 3.3 doesn't
> have an MPEG decoder, AFAIK.

ok, I stand corrected.

I must have mixed something up. Someone claimed it had something which did  
MPEG and used one of available MPEG packages.

> Yes and no - this is really two-fold. Of course braind-dead TCP/IP isn't very
> useful on either really- high-speed or low-bandwith networks, reliable or
> not. See the ATM standards commitees and vendors bending over backwards in
> order to achieve high throughput over these nice 155/622 mbit/sec links..
>
> Of c(o)urse, the real problem is not so much the transmission itself, but
> rather client presentation. Since HTML combines the worst features of both

Well, we have two problems ...

a) layout, etc.
b) multiple data streams

I don't mixing these two things together is a good idea
a) is a HTML problem
b) is HTTP, etc, etc. esp audio video should other protocols than http.

The URL gives what b) to use.

So all it is given, but noone uses this right. Notable exception: bolo on the Mac.

> Anyway, this is all pretty academic, because NetScape don't give a flying
> [bad four-letter word here] - and amazingly enough, everybody seems to like
> getting their multimedial future shaped by a company that has about as much
> strategy like a dead fish on the beach.

Unfortunatly this seems to be true...

  Wolfgang