Hi Pier,

I know we discussed that, but I want to make sure everything is ok - 
I would like to implement the java side of "warp" in tomcat3.3, and 
reuse the C side from 4.0.

Would it be ok to make a symbolic link, so the native code is in sync ?
It's the simplest way to do that ( and I tested it - works fine ).

I will not make any change ( without asking you first :-), but I want the
C sources to be available in the 3.3 workspace.

( it'll be linked to jakartat-tomcat/src/native/mod_warp )

Costin


On Thu, 30 Nov 2000, Pier P. Fumagalli wrote:

> [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > 
> > Added:       catalina/src/share/org/apache/catalina/connector/warp
> >                       WarpConnection.java
> >                       WarpConnectionHandler.java
> >                       WarpConstants.java
> >                       WarpDebug.java
> >                       WarpHandler.java
> >                       WarpHandlerTable.java
> >                       WarpPacket.java
> >                       WarpReader.java
> 
> Ok, in an "impetus" of passion yesterday evening I rewrote the protocol...
> Now, what does that mean? It means that now the protocol supports
> multiplexing; take a look at the AJPv20 and v21 specs... v20 was designed
> with multiplexing in mind, but it was dropped in v21 because it was too
> difficult to implement. Well, it's not (Nice when after two years I prove
> myself wrong :)
> Checked in there are all the "basic" classes and C sources, those dealing w/
> packets, multiplexing, data transfer, blablabla... (Check out the
> WarpHandler since it's a HELL of synchronization, please... It runs with
> approximately loads of 1000 packets received and sent at the same time, but
> more eyes, less bugs).
> Now I'm integrating those in Catalina...
> 
>     Pier (who is starting to feel almost like a vampire!)
> 
> 

Reply via email to