RE: [Mod-pubsub-developer] Re: Quick question...

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4417.0">
<TITLE>RE: [Mod-pubsub-developer] Re: Quick question...</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>

<P><FONT SIZE=3D2>&gt; There is an sourceforge project called 'destiny' =
that is an HTTP </FONT>

<BR><FONT SIZE=3D2>&gt; bridge to JMS.</FONT>
</P>

<P><FONT SIZE=3D2>Excellent suggestion.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; You could use that as a starting point to =
implement that same HTTP API </FONT>

<BR><FONT SIZE=3D2>&gt; used by mod-pubsub. </FONT>
</P>

<P><FONT SIZE=3D2>Were can I find (either files in distribution or docs) =
details on the HTTP API?</FONT>

<BR><FONT SIZE=3D2>Is there any info on the mechanism used by mod-pubsub =
for the keep alive connection?</FONT>

<BR><FONT SIZE=3D2>I am assume this is accomplished by both, having =
'keep-alive' plus other info in the header?</FONT>
</P>

<P><FONT SIZE=3D2>Oliver Muoto</FONT>

<BR><FONT SIZE=3D2>ol...@mu...</FONT>
</P>

</BODY>
</HTML>