GOMEZ Henri wrote:
> >The reason I ask is that I think the mod_jk C code (the
> >various modules which plug into the web servers), is actually
> >extremely well-written and flexible. It's totally
> >undocumented, but, if necessary, I'd be willing to remedy that
> >(I don't mind writing documentation). One of the best things
> >about that C code is that it allows many different web servers
> >to talk to many different protocols in a very clean way. So I
> >wonder if it would be possible to make it to also talk
> >whatever protocol you're developing as part of mod_webapp.
> >
> >This would mean basically merging mod_webapp into mod_jk (or
> >merging mod_jk into mod_webapp, depending on your perspective ;-).
>
> Just a little comment.
>
> I've builded the mod_webapp module and it fail when session are in use.
> May be related to cookies support. I could tell you more later after
> some capture with ethereal.
>
Finally, someone actually trying it so we can fix the bugs :-)
>
> I wonder if mod_webapp will support Load Balancing and Fault Tolerance.
> It's not clear in Directives.
>
I've asked Pier to document what he has described to me informally as goals for
the mod_webapp design, but this is definitely on the list of desireable things
to support. Of course, getting the basic stuff working right first is
important.
>
> Another point of mod_jk is for Dan and about the question of security
> and or ligth crypto support. ajp12/ajp13 didn't support ACL to accept/deny
> connections from a list of known host, and the protocol is in clear text.
> Costin suggest using SSH tunnels which be a fast work-around but I really
> like to have this ACL+CRYPTO included in mod_jk/ajp13.
>
> Did mod_webapp will support ACL/CRYPTO ? Even if crypto is not easily
> exportable
> even mod_ssl is such relaxed now that it could be used in Redhat
> Distributions (6.2/7.0)
>
The code inside mod_webapp is layered, with precisely this type of use in mind.
>
> >What do you think of this course of action? I'm hoping that
> >you and I can align our efforts so that we can take as much
> >advantage of each other's work as possible.
>
> Count me on.
Craig
