> , the code put up at nodejs also has the same problem
That's not good.
On Sun, Mar 4, 2012 at 1:19 AM, puneeth poduri wrote:
> Thank you , i must be doing wrong i'll post the code once i am sure
> there are no errors in it . guess i'll have to read up on architecture
> of node . One more thin
Thank you , i must be doing wrong i'll post the code once i am sure
there are no errors in it . guess i'll have to read up on architecture
of node . One more thing , the code put up at nodejs also has the same
problem . may be it is the way the httperf behaves . i'll try and
rectify it. thank you o
> does the internal node.js send a reset connection back to avoid blocking
It isn't doing anything tricky like that. It just accepts a connection,
sets up a stream, and calls you back. The blocking is avoided by the
architecture of node which much is written about.
On Sat, Mar 3, 2012 at 10:31
thank you @mark i will try and run the test on the code given at
node.js , i was following a tutorial on how to make web applications
and i wanted to do something more so i wrote a http server looks like
it is working fine there is no problem if i view the page on a
browser. i just have to fine tu
