ed0907bb
From: grahn+nntp@snipabacken.se
On Sat, 2010-02-20, karthikbalaguru wrote:
> On Feb 20, 8:56 pm, Jorgen Grahn wrote:
>> ["Followup-To:" header set to comp.protocols.tcp-ip.]
>>
>> On Sat, 2010-02-20, karthikbalaguru wrote:
>> > On Feb 9, 1:30 pm, "Boudewijn Dijkstra"
>> > wrote:
>>
>> [long discussion held elsewhere than in comp.protocols.tcp-ip]
>>
>>
>>
>> >> 70 [µs] = 700 [bytes] / 80 [Mbit/s]
>>
>> > Okay :-)
>>
>> > While reading about the various designs, interestingly i
>> > came across an info that the design of TCP servers is
>> > mostly such that whenever it accepts a connection
>>
>> ...
>>
>> Ugh. Please don't crosspost that widely, and especially don't include
>> additional groups in mid-thread without saying so in your posting.
>>
>> It makes me reluctant to answer your question, because I don't know if
>> the comp.arch.embedded and comp.os.linux.networking crowds want to
>> hear me, or if they'd rather not see the rest of the thread. I don't
>> know what's on topic there, because I don't read those groups. See the
>> problem?
>>
>
> Okay !
>
> In TCP server
> whenever a new connection arrives, it accepts the
...
> a new process for every new connection ? How is
> it being managed ?
>
> More importantly,
...
> design is based on only one process ?
>
> Consider a scenario that there are
...
> Any ideas ?
You misunderstood me. The damage is already done -- repeating a
variation of the question (I assume; I didn't read it) once more
without crossposting isn't useful. Not to me at least -- I have
already wasted too much of my time on this.
/Jorgen
--
// Jorgen Grahn O o .
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
