[Zope-dev] how to reach Zpublisher without passing by ZServer ?
Olivier Moïses
contact@generic-concept.com
Wed, 27 Feb 2002 18:32:36 +0100
This is a multi-part message in MIME format.
------=_NextPart_000_002E_01C1BFBD.2108BEF0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by smtp-2.nordnet.fr id g1RHWPVq022866
Hello,
Does anyone know how to reach Zpublisher without passing by Zserver from =
any
client ?
I explain my question :
I would like to send XML Fragments from a client (Mozilla) to Zope. But, =
in
HTTPRequest.py, I read that when the content-type of the request is
=91text/xml=92 and the method is =91post=92 (exactly like in most of the =
cases I
process), automatically, Zope process the request as XML-RPC.
The XML-RPC only support ASCII (7-bits characters encoding) in the specs,
and I want to encode at least UTF-8 in request and response. I could base=
64
encode all my data, but I would like to avoid the overloading of this
encoding.
Is there a (simple) way to add another protocol than XML-RPC, Webdav, HTT=
P,
and FTP to Zope ?
Is there a cool way to extend Zserver, or directly access the ZPublisher
from another source ?
Regards
Olivier Moises
------=_NextPart_000_002E_01C1BFBD.2108BEF0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C1BFBD.20D8FC60">
<!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:DoNotRelyOnCSS/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:DocumentKind>DocumentEmail</w:DocumentKind>
<w:HyphenationZone>21</w:HyphenationZone>
<w:EnvelopeVis/>
</w:WordDocument>
</xml><![endif]-->
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0cm;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
{margin:0cm;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
span.StyleCourrierlectronique15
{mso-style-type:personal-compose;
mso-ansi-font-size:10.0pt;
mso-ascii-font-family:Arial;
mso-hansi-font-family:Arial;
mso-bidi-font-family:Arial;
color:black;}
@page Section1
{size:595.3pt 841.9pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;
mso-header-margin:35.4pt;
mso-footer-margin:35.4pt;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=3DFR style=3D'tab-interval:35.4pt'>
<div class=3DSection1>
<p class=3DMsoNormal><span class=3DStyleCourrierlectronique15><font =
size=3D2
color=3Dblack face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial;mso-ansi-language:EN-GB'>Hello,<o:p></o:p></span=
></font></span></p>
<p class=3DMsoNormal><span class=3DStyleCourrierlectronique15><font =
size=3D2
color=3Dblack face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial;mso-ansi-language:EN-GB'><![if =
!supportEmptyParas]> <![endif]><o:p></o:p></span></font></span></p>
<p class=3DMsoNormal><span class=3DStyleCourrierlectronique15><font =
size=3D2
color=3Dblack face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial;mso-ansi-language:EN-GB'>Does anyone know how =
to reach
Zpublisher without passing by Zserver from any client =
?<o:p></o:p></span></font></span></p>
<p class=3DMsoNormal><span class=3DStyleCourrierlectronique15><font =
size=3D2
color=3Dblack face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial;mso-ansi-language:EN-GB'><![if =
!supportEmptyParas]> <![endif]><o:p></o:p></span></font></span></p>
<p class=3DMsoNormal><span class=3DStyleCourrierlectronique15><font =
size=3D2
color=3Dblack face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial;mso-ansi-language:EN-GB'>I explain my question =
:<o:p></o:p></span></font></span></p>
<p class=3DMsoNormal><span class=3DStyleCourrierlectronique15><font =
size=3D2
color=3Dblack face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial;mso-ansi-language:EN-GB'><![if =
!supportEmptyParas]> <![endif]><o:p></o:p></span></font></span></p>
<p class=3DMsoNormal><span class=3DStyleCourrierlectronique15><font =
size=3D2
color=3Dblack face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial;mso-ansi-language:EN-GB'>I would like to send =
XML
Fragments from a client (Mozilla) to Zope. But, in HTTPRequest.py, I =
read that
when the content-type of the request is ‘text/xml’ and the =
method is ‘post’
(exactly like in most of the cases I process), automatically, Zope =
process the request
as XML-RPC.<o:p></o:p></span></font></span></p>
<p class=3DMsoNormal><span class=3DStyleCourrierlectronique15><font =
size=3D2
color=3Dblack face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial;mso-ansi-language:EN-GB'>The XML-RPC only =
support
ASCII (7-bits characters encoding) in the specs, and I want to encode at =
least
UTF-8 in request and response. I could base64 encode all <span
style=3D"mso-spacerun: yes"> </span>my data, but I would like to =
avoid the
overloading of this encoding.<o:p></o:p></span></font></span></p>
<p class=3DMsoNormal><span class=3DStyleCourrierlectronique15><font =
size=3D2
color=3Dblack face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial;mso-ansi-language:EN-GB'><![if =
!supportEmptyParas]> <![endif]><o:p></o:p></span></font></span></p>
<p class=3DMsoNormal><span class=3DStyleCourrierlectronique15><font =
size=3D2
color=3Dblack face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial;mso-ansi-language:EN-GB'>Is there a (simple) =
way to add
another protocol than XML-RPC, Webdav, HTTP, and FTP to Zope =
?<o:p></o:p></span></font></span></p>
<p class=3DMsoNormal><span class=3DStyleCourrierlectronique15><font =
size=3D2
color=3Dblack face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial;mso-ansi-language:EN-GB'>Is there a cool way to =
extend
Zserver, or directly access <span style=3D"mso-spacerun: =
yes"> </span>the ZPublisher
from another source ?<o:p></o:p></span></font></span></p>
<p class=3DMsoNormal><span class=3DStyleCourrierlectronique15><font =
size=3D2
color=3Dblack face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial;mso-ansi-language:EN-GB'><![if =
!supportEmptyParas]> <![endif]><o:p></o:p></span></font></span></p>
<p class=3DMsoNormal><span class=3DStyleCourrierlectronique15><font =
size=3D2
color=3Dblack face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial;mso-ansi-language:EN-GB'>Regards<o:p></o:p></spa=
n></font></span></p>
<p class=3DMsoNormal><span class=3DStyleCourrierlectronique15><font =
size=3D2
color=3Dblack face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial;mso-ansi-language:EN-GB'><![if =
!supportEmptyParas]> <![endif]><o:p></o:p></span></font></span></p>
<p class=3DMsoNormal><span class=3DStyleCourrierlectronique15><font =
size=3D2
color=3Dblack face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial;mso-ansi-language:EN-GB'>Olivier =
Moises</span></font></span><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font><=
/p>
</div>
</body>
</html>
------=_NextPart_000_002E_01C1BFBD.2108BEF0--