"First packet" may not always be the first packet, given Connection:
keep-alive. Basically what I'm saying is that there are no guarantees that
this will continue working, or work consistently. You seem to have a good
understanding of the risks involved, but for me I'd sooner use
child_process.spawn('curl', [url]) over the monkey patch.On Tue, Jan 8, 2013 at 7:34 PM, Matt <[email protected]> wrote: > On Tue, Jan 8, 2013 at 5:24 PM, Marcel Laverdet <[email protected]>wrote: > >> By heavy load I'm talking about network traffic, either on your end, >> their end, or any hop in between. "In the first packet" is certainly *not* >> something I'd recommend anyone to depend on, as that depends on a whole lot >> of things. >> > > Not really - TCP is more reliable that way than you think. No matter the > load, that first "packet" isn't going to get fragmented to any smaller > parts. Especially since it's actually SSL, so it's not even really a > packet, but an event in node happening, with buffering already taking place. > > -- > 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 > -- 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
