W3C home > Mailing lists > Public > www-jigsaw@w3.org > March to April 1999

Re: What classes to override to do RTSP?

From: Brian Dupras <bdupras@bigfoot.com>
Date: Tue, 6 Apr 1999 14:15:54 -0400 (EDT)
Message-ID: <00b901be8059$6a1a3660$d146b5d1@dnvr.uswest.net>
To: "Gary Teter" <bigdog@bulldogbeach.com>, "jigsaw" <www-jigsaw@w3.org>
> ... because it has to communicate through an HTTP
> interface (at least all the ones I've written before do).

Actually, a servlet can do anyhting that the host environment will allow.
I've seen a servlet that does one task, but serves up multiple interfaces:
HTTP via the standard servlet stuff, *and* a direct open socket, *and* RMI
(CORBA).  The client(s) can choose which interface to use.

The example is in McGraw Hill's "Java Servlets" by Karl Moss.  It's pretty
cool.

B


----- Original Message -----
From: Gary Teter <bigdog@bulldogbeach.com>
To: Brian Dupras <bdupras@bigfoot.com>
Sent: Tuesday, April 06, 1999 12:05 PM
Subject: Re: What classes to override to do RTSP?


> Brian Dupras <bdupras@bigfoot.com>, on 4/6/99 10:58 AM wrote:
>
> >You might consider writng your server "extension" as a java servlet.
Once
> >loaded, a HTTP servlet by default has a sessioning mechanism.  This could
> >help you get around the stateless protocol of HTTP.
> >
> >If written as a servlet, you can also transport the servlet across
multiple
> >web servers such as Jigsaw, Apache, IIS, Netscape, JWS, etc.
> >
> >Brian
>
> Hmmm. That's an interesting idea that I hadn't thought of before.
>
> But the RTSP spec, while it has a lot of the same request and response
> messages as HTTP, has some other things in it that I don't think a
> servlet could support because it has to communicate through an HTTP
> interface (at least all the ones I've written before do).
>
> I'm thinking I'll have to go a few layers deeper into Jigsaw than just
> the servlet api to do it.
>
> --
> Gary Teter, Big Dog
> Bulldog Beach Interactive http://www.bulldogbeach.com
>
>
Received on Tuesday, 6 April 1999 15:21:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:29 GMT