I’m having a strange issue with faye/nodejs where the page appears to be loading for a long time on an initial page load due to a /meta/connect call. This page load appears to last for exactly 45s (which is the value of the timeout set on the server)
Here are the details of the call:
The call in question is the following:
params:
jsonp: __jsonp3__
message: [{“channel”:”/meta/connect”,”clientId”:”0c3gocq1rwi3sl0dskn4u00e8wj7″,”connectionType”:”callback-polling”,”id”:”5″}]
response:
__jsonp3__([{“id”:”5″,”clientId”:”0c3gocq1rwi3sl0dskn4u00e8wj7″,”channel”:”/meta/connect”,”successful”:true,”advice”:{“reconnect”:”retry”,”interval”:0,”timeout”:45000}}]);
I’ve tried it without SSL, but the problem still persists, so it doesn’t appear to be related to that.
The page is completely responsive during this time, but it’s obviously an issue for my customers as they just see the loading bar in ff or chrome and they end up waiting the full 45 seconds for it to stop before proceeding. Any help in debugging or mitigating this issue is appreciated; possibly making the initial connect call asynchronous so it doesn’t trigger on an initial page load?
I’ve also posted on the faye google group here: https://groups.google.com/forum/?fromgroups#!topic/faye-users/xZI4adt3DpA%5B1-25%5D
But I have not gotten a reply yet, though it does seem that I am not the only one with this issue.
Any help is appreciated.
Thanks!
Kevin
Just in case any future googlers stumble on this topic: the issue in question has been resolved in the newer versions of Faye. There are some further details on the google group link in my original question – the issue should be fixed as of faye 0.8.4 (currently 0.8.6)
I can confirm that this fixed the issue for me, I no longer see any timeouts on page load.