yeah thats a good point .. i did noticed that for long response requests it tends to disconnect the client and then the response never completes .. however i am using socket.io so isnt that supposed to use websockets for chrome and it still ends up disconnecting the client
infact another thing I noticed is that if the application is monitoring logs by tailing a file and receiving log file updates and at the same time if i trigger a heavy search which sends a bunch of data back then then tail process gets stuck as well .. after doing some search the only thing i came across was to utilize process.nextTick in the search process to let the tail processes continue .. havent incorporated that yet to see if that improves things.. On Tuesday, July 3, 2012 9:54:40 AM UTC-5, mscdex wrote: > > On Jul 3, 10:25 am, Adeel Qureshi <[email protected]> wrote: > > hmm conflicting answers :) i guess ill try to run a test with a lot of > data > > and see which approach works more consistent .. meaning doesnt leads to > > disconnects .. thanks for the input .. ill post my findings > > Additionally, in case the client disconnects before the operation is > complete, they would have at least some data if you did it the > streaming way. If you are worried about connection/disconnection > overhead, you might look into using a long lived connection instead of > long polling, such as websockets, server-sent events, and/or xhr > multipart streaming. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
