punjab-devel — Punjab development discussion

[Punjab-devel] Punjab HTTP Binding

[Ramon A. D. <rd...@wo...>]

Thank you so much for your work on Punjab.  The project is really
filling a unique niche, and I was grateful to have come accross it.
=20
My only issue is that HTTP Binding isn't working quite the way I thought
it should.  The current HTTP Binding interface returns a response to the
client immediately even if it has no new message (empty body).  And then
the client immediately submits a new request because that's what it is
supposed to do for HTTP Binding.  What results is just HTTP Polling with
pretty much instant polling rate (and therefor uses even more bandwidth
than pure HTTP Polling).
=20
The way I thought HTTP Binding was supposed to work was to wait up to
the client specified wait time before returning a reply, unless a
message becomes available for the client.  Then it can return the
message, but otherwise it should wait until the wait time has expired
before sending back the empty body.
=20
I'm new to Python and Twisted so I'm not exactly sure where to start
looking for adding this behavior.  Please provide a few pointers and
I'll be glad to try adding it on my own.  Thanks.
=20
Ray

[Punjab-devel] A question about logging out

[Jason S. <js...@fr...>]

I have the newest version of Punjab running and I am testing it out to
see if I get any logouts... but one question i do have is this. When i
close the jwchat browser, do I need to log out? How do I get the current
user to log out. As of right now the user hangs around for about 10
minutes or so before being logged out. If this is a jwchat problem I
will take it over there... but thought i would ask here :)

I tried both IE 6 and FireFox 1.0.4, both leave the user hanging. Got to
love these mysteries.

Since you asked that we switch to the mailing list... I thought I would
resend this just in case it was overlooked.

[Punjab-devel] punjab xmlrpc problem

[Mickael R. <mic...@er...>]

Hello,

I have detected a small problem in Punjab release 0.5. I do not know if 
it has been fixed in CVS.

I found that xmlrpc disconnect return a fault message even if 
disconnection seems to have been successfull at the Jabber level.

Here is the fault message sent back:

  - << "HTTP/1.1 200 OK[\r][\n]"
  - << "Date: Fri, 25 Mar 2005 10:31:05 GMT[\r][\n]"
  - << "Content-length: 278[\r][\n]"
  - << "Content-type: text/xml[\r][\n]"
  - << "Server: TwistedWeb/1.3.0rc1[\r][\n]"
  - << "<?xml version='1.0'?>[\n]"
  - << "<methodResponse>[\n]"
  - << "<fault>[\n]"
  - << "<value><struct>[\n]"
  - << "<member>[\n]"
  - << "<name>faultCode</name>[\n]"
  - << "<value><int>8002</int></value>[\n]"
  - << "</member>[\n]"
  - << "<member>[\n]"
  - << "<name>faultString</name>[\n]"
  - << "<value><string>Error in disconnect.</string></value>[\n]"
  - << "</member>[\n]"
  - << "</struct></value>[\n]"
  - << "</fault>[\n]"
  - << "</methodResponse>[\n]"

I have installed Twisted 1.3.0 with all recommanded patch.

It seems to work when I replace s.expire() by s.disconnect() in xmlrpc.py

I hope this helps,

-- 
Mickaël Rémond
  http://www.erlang-projects.org/