9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jonathan Sergent <sergent@etla.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Gecko based web browser
Date: Wed, 19 Jul 2000 15:23:22 +0000	[thread overview]
Message-ID: <slrn8nbgad.h0h.sergent@c61066-a.frmt1.sfba.home.com> (raw)
In-Reply-To: <200007190718.DAA24199@cse.psu.edu>

On Wed, 19 Jul 2000 07:54:18 GMT,
forsyth@caldo.demon.co.uk <forsyth@caldo.demon.co.uk> wrote:
>it's only available via binary plug-ins, and some -- perhaps many -- of those
>only work under windows (and sometimes only within
>a browser, though that might not be true of realaudio).
>by `format' i meant the whole thing.
>it seems a bit pointless to implement the transport without being
>able to replay the sounds it contains.

There are RTP (RFC 1889) payload types for several compression algorithms
which are free, and that could be implemented without too much trouble.

I'm not sure how hard it is to get Real's server to stream most of them,
but Apple's QuickTime streaming stuff (also controlled by RTSP, RFC 2326)
supports several standard codecs and standard RTP payload types for audio
and video.  (They have their proprietary formats as well, but it's not
hard to produce content in the free codecs; they just aren't typically
as well suited for low bitrate streaming or aren't as high quality).

It's not hard to throw together a simple RTSP and RTP client.  For some
of the easy audio codecs (i.e. uLaw) it should be fairly simple to throw
together something to do playback for Plan 9.  I think the JPEG stuff
should probably be easy with reuse of the existing JPEG display code once
you depacketize the stuff.  The RTSP part could probably be done in rc.

You usually don't have to do much of a browser plugin for these things.
There's nothing wrong with showing it in another window.  The page
does often use an EMBED tag but you could send those to the plumber
and have it know to pop up the RTSP client for it.

Getting a server for this stuff on Plan 9 is probably a bit more
challenging...


--jss.


  parent reply	other threads:[~2000-07-19 15:23 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-19  7:18 forsyth
2000-07-19  7:43 ` Lucio De Re
2000-07-19  7:58 ` Randolph Fritz
2000-07-19 15:23 ` Jonathan Sergent [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-07-26 17:43 miller
2000-07-26 17:50 ` James G. Stallings II
2000-07-27  7:43   ` Matt
2000-07-27  7:54     ` Lucio De Re
2000-07-27 17:28       ` Matt
2000-07-20  4:05 James A. Robinson
2000-07-20  1:41 rob pike
2000-07-20  8:34 ` George Coulouris
2000-07-18 23:02 forsyth
2000-07-18 22:30 ` Frank Gleason
2000-07-19  0:17   ` Randolph Fritz
2000-07-19  0:01     ` Frank Gleason
2000-07-19  1:02 ` Skip Tavakkolian
2000-07-19 11:45 ` Theo Honohan
2000-07-18 22:33 rob pike
2000-07-18 22:59 ` Howard Trickey
2000-07-21  8:34 ` Alt
2000-07-25 15:07   ` Douglas A. Gwyn
2000-07-18 20:23 miller
2000-07-18 22:07 ` Randolph Fritz
2000-07-18 19:03 Stephen Harris
2000-07-18 19:17 ` Andrey Mirtchovski
2000-07-18 23:48   ` Randolph Fritz
2000-07-19  5:40     ` Randolph Fritz
2000-07-19  9:26   ` Michael Dingler
2000-07-19 15:22   ` Douglas A. Gwyn
2000-07-19 16:28     ` Andrey Mirtchovski
2000-07-19 16:47       ` Randolph Fritz
2000-07-19 22:52       ` sah
2000-07-20  1:16         ` James A. Robinson
2000-07-20  3:08         ` Boyd Roberts
2000-07-26  8:42     ` Ralph Corderoy
2000-07-19  9:27 ` Christopher Browne
2000-07-19 15:24   ` Andy Newman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=slrn8nbgad.h0h.sergent@c61066-a.frmt1.sfba.home.com \
    --to=sergent@etla.net \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).