- From: Brian Dupras <bdupras@bigfoot.com>
- Date: Tue, 6 Apr 1999 13:59:09 -0400 (EDT)
- To: "Gary Teter" <bigdog@bulldogbeach.com>, "jigsaw" <www-jigsaw@w3.org>
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 ----- Original Message ----- From: Gary Teter <bigdog@bulldogbeach.com> To: W3 Jigsaw Mailinglist <www-jigsaw@w3.org> Sent: Tuesday, April 06, 1999 11:03 AM Subject: What classes to override to do RTSP? > Sorry to repost a question, but I didn't receive any response, and I > don't know where else to ask... > > Can anyone give me some guidelines as to which classes I should be > overriding so I can write an addition to Jigsaw to make it function as an > RTSP server? > > >From the architecture, it looks like I'll need to do more than just > create a new resource, since RTSP assumes that connections have state, > unlike HTTP. > > Am I heading in the right direction if I create a new package that > implements everything in org.w3c.www.protocol.http? It looks like I'll > have to do more than just that, but I need some help deciding what to > do.... > > I'm not looking for a completed solution here (unless there is one :-), > just some pointers in the right direction. > > Thanks in advance for any help/guidance/tips/pointers anyone can offer! > > -- > Gary Teter, Big Dog > Bulldog Beach Interactive http://www.bulldogbeach.com > > >
Received on Tuesday, 6 April 1999 14:00:31 UTC