Hi, everyone: I've been tasked by my school to implement some type of near-real-time notification system that we can install on all of our computers on campus (2000+). A Pubsubhubub type system sounded ideal, and I convinced my boss to let me prototype something locally to see if it would really work for us. So far, I'm pleased with how well it's working, but I'm come across a strange problem with communication between the hub and our client.
For a hub, our test environment is using a local linux box running pubsubhubbub, as described in the Developer's getting started guide on the wiki. For a publisher, I'm using the tubes example also from the wiki. My client is a home-grown VB.NET app I've thrown together. On a very simple level, all it does is send subscription requests to the hub, and wait for the hub to communicate with it. I've had no problems when I try to subscribe to a feed with my client, but I do have some strange behavior when my client receives a subscription update. It appears that the hub is only sending the header information to my client, but no body. For example, here's what my client received the last time the hub tried to send it an update (between the quotes): "POST / HTTP/1.1 Content-Length: 759 Accept-Encoding: gzip X-Hub-Signature: sha1=26defdc3c19b0292972562491226ad024fc5ba3e User-Agent: AppEngine-Google; (+http://code.google.com/appengine) Host: 10.14.101.112:1918 Referer: http://localhost/ Content-Type: application/atom+xml " There appears to be nothing wrong in the communication chain. The publisher updates the hub, and the hub communicates with the clients. Everything works until the client receives the POST header, then nothing. The hub shows no error messages, until a few seconds when it reports that it's timed out waiting for a response. (Of course there's no response, there's nothing to respond to. However, I tried hardcoding a 200 response code after I received the data above, but same problem.) Has anyone else run across a similar situation? Any help/direction/ ideas would be appreciated at this point. Thanks! Mark
