Re: [Zope] POST sucks.

2006-09-14 Thread Paul Winkler
On Wed, Sep 13, 2006 at 10:02:56AM +0200, Igor Stroh wrote: Doing a lot web services developoment lately, I find tcpflow? very usefull (and much easier to use then ethereal), e.g.: `tcpflow -c -i eth0 port 8080` will sniff on port 8080 (interface eth0) in interactive mode, so you'll see the

Re: [Zope] POST sucks.

2006-09-13 Thread Igor Stroh
Paul Winkler wrote: On Tue, Sep 12, 2006 at 07:40:15PM +0200, Andreas Jung wrote: Ethereal aka Wireshark how it is called now works perfectly for any kind of network analysis like that. It has a functionality Follow TCP stream and is able to decode nearly every protocol. Oooh, that looks

[Zope] POST sucks.

2006-09-12 Thread Paul Winkler
Been doing web services (XML-RPC) stuff lately. What suggestions do people have for troubleshooting a zope-based XML-RPC application? Access and trace logs are totally useless, since even the method name is hidden in the POST payload, so I feel like I'm flying blind; when a client developer tells

Re: [Zope] POST sucks.

2006-09-12 Thread Andrew Milton
+---[ Paul Winkler ]-- | Been doing web services (XML-RPC) stuff lately. | What suggestions do people have for troubleshooting a zope-based | XML-RPC application? When debugging; o Raise an exception from python scripts, you can include some info in it. o Use FireFox and

Re: [Zope] POST sucks.

2006-09-12 Thread Paul Winkler
On Wed, Sep 13, 2006 at 02:39:14AM +1000, Andrew Milton wrote: +---[ Paul Winkler ]-- | Been doing web services (XML-RPC) stuff lately. | What suggestions do people have for troubleshooting a zope-based | XML-RPC application? When debugging; o Raise an exception

Re: [Zope] POST sucks.

2006-09-12 Thread Willi Langenberger
According to Paul Winkler: Been doing web services (XML-RPC) stuff lately. What suggestions do people have for troubleshooting a zope-based XML-RPC application? Access and trace logs are totally useless, since even the method name is hidden in the POST payload, so I feel like I'm flying

Re: [Zope] POST sucks.

2006-09-12 Thread Andrew Milton
+---[ Paul Winkler ]-- | On Wed, Sep 13, 2006 at 02:39:14AM +1000, Andrew Milton wrote: | +---[ Paul Winkler ]-- | | Been doing web services (XML-RPC) stuff lately. | | What suggestions do people have for troubleshooting a zope-based | | XML-RPC

Re: [Zope] POST sucks.

2006-09-12 Thread Andreas Jung
--On 12. September 2006 12:34:38 -0400 Paul Winkler [EMAIL PROTECTED] wrote: Been doing web services (XML-RPC) stuff lately. What suggestions do people have for troubleshooting a zope-based XML-RPC application? Access and trace logs are totally useless, since even the method name is hidden

Re: [Zope] POST sucks.

2006-09-12 Thread Paul Winkler
On Tue, Sep 12, 2006 at 07:40:15PM +0200, Andreas Jung wrote: Ethereal aka Wireshark how it is called now works perfectly for any kind of network analysis like that. It has a functionality Follow TCP stream and is able to decode nearly every protocol. Oooh, that looks really really useful.

Re: [Zope] POST sucks.

2006-09-12 Thread Paul Winkler
On Wed, Sep 13, 2006 at 03:04:48AM +1000, Andrew Milton wrote: +---[ Paul Winkler ]-- | On Wed, Sep 13, 2006 at 02:39:14AM +1000, Andrew Milton wrote: | +---[ Paul Winkler ]-- | | Been doing web services (XML-RPC) stuff lately. | | What

Re: [Zope] POST sucks.

2006-09-12 Thread Paul Winkler
On Tue, Sep 12, 2006 at 06:58:36PM +0200, Willi Langenberger wrote: I found it very useful to log every xml-rpc call (call and return value). For this we have patched ZPublisher/xmlrpc.py (and one line in ZPublisher/HTTPRequest.py). See attachment (tested against 2.9.3). (snip) Thanks! I may