durusmail: quixote-users: Re: Pipelining the async HTTP server
async HTTP server included?
2004-01-06
2004-01-06
Re: async HTTP server included?
2004-01-06
2004-01-06
async HTTP server included?
2004-01-06
Re: async HTTP server included?
2004-01-06
async HTTP server included?
2004-01-07
Re: async HTTP server included?
2004-01-07
2004-01-07
2004-01-07
2004-01-07
Re: Licensing
2004-01-07
2004-01-07
2004-01-07
Pipelining the async HTTP server
2004-01-07
Re: Pipelining the async HTTP server
2004-01-07
2004-01-07
2004-01-08
Re: Pipelining the async HTTP server
2004-01-08
2004-01-08
2004-01-08
2004-01-08
quixote.server.medusa (Re: Pipelining the async HTTP server)
2004-01-08
quixote.server.medusa
2004-01-08
2004-01-12
Re: quixote.server.medusa (Re: Pipelining the async HTTP server)
2004-01-13
Problem with using quixote.server.medusa vs. standalone medusa
2004-01-14
Re: Problem with using quixote.server.medusa vs. standalone medusa
2004-01-14
Resolved! Was Re: [Quixote-users] Re: Problem with using quixote.server.medusa vs. standalone medusa
2004-01-14
Re: Resolved! Was Re: Re: Problem with using quixote.server.medusa vs. standalone medusa
2004-01-14
Pipelining the async HTTP server
2004-01-08
2004-01-08
Re: Pipelining the async HTTP server
2004-01-08
2004-01-08
2004-01-06
Re: async HTTP server included?
2004-01-06
Re: Pipelining the async HTTP server
Mark Bucciarelli
2004-01-08
On Thursday 08 January 2004 9:46 am, A.M. Kuchling wrote:
> On Thu, Jan 08, 2004 at 08:36:26AM -0500, Mark Bucciarelli wrote:
> >If Medusa does come to be included, I'd like to request that you incliude
> >Medusa's xmlrpc handler.  My app uses Medusa as a Quixote server and and
> >XmlRpc server.
>
> Is the XML-RPC server on a different port from the HTML-serving HTTP
> server? I'm wondering why you don't just handle the XML-RPC in Quixote,
> perhaps using util.xmlrpc, perhaps not.

Yes, the same port.  I didn't know about util.xmlrpc.  :(

BTW, Dirda does write extremely well.  :)

Regards,

Mark


reply