Using Zope as App Server for non http-Protocols
We want to (mis)use zope as an application server servicing a proprietary non-http protocol for transmitting compressed data. Our idea is a specially written client that connects on a proprietary port to zope where a special product is listening and serving the request. Our question: How can I implement a product listening on a specific port and servicing requests and sending back binary (in our case compressed) data. But the product should of course be able to use the infrastructure of Zope (ODB,External methods,ZSQL methods...) Another question is how does the authentification work for such a non-http connection. Any hints? Thanks in advance Philipp Auersperg
On Fri, 11 Aug 2000 23:30:43 +0200, "Philipp Auersperg" <zope@philosoft.at> wrote:
We want to (mis)use zope as an application server servicing a proprietary non-http protocol for transmitting compressed data.
Its easy to overlook http if your application is not a conventional 'web' application, but there are strong reasons for sticking with http if possible: you can benefit from the existing tools and infrastructure, plus Zope already talks http. SOAP looks like it will be popular for similar reasons. What do you need to do that makes http unsuitable? Toby Dickenson tdickenson@geminidataloggers.com
participants (2)
-
Philipp Auersperg -
Toby Dickenson