-
From: Guillaume Cottenceau g...@mnc.ch
To: Stipe Tolj s...@tolj.org
Cc: devel Devel devel@kannel.org
Sent: Wednesday, May 06, 2009 7:28 PM
Subject: Re: singlethreaded or multithreaded
Stipe Tolj st 'at' tolj.org writes:
The HTTP client layer in gwlib/http.[ch] works this way:
We look
What do you mean by DLR request?
Kannel asks the SMSC to report back. The SMSC will report whenever
something is happening and kannel forwards it to http.
On 06.05.2009, at 16:18, Beatrice Tamburrino wrote:
hi,
how does kannel send the dlr-requests? sequentiell? or pararell
Andreas Fink afink 'at' list.fink.org writes:
What do you mean by DLR request?
Kannel asks the SMSC to report back. The SMSC will report whenever
something is happening and kannel forwards it to http.
In the context, I suppose the question was about
kannel-application DLR transport (HTTP),
: singlethreaded or multithreaded
What do you mean by DLR request?
Kannel asks the SMSC to report back. The SMSC will report whenever
something is happening and kannel forwards it to http.
On 06.05.2009, at 16:18, Beatrice Tamburrino wrote:
hi,
how does kannel send the dlr-requests? sequentiell
exactly :)
Original-Nachricht
Datum: Wed, 06 May 2009 16:27:03 +0200
Von: Guillaume Cottenceau g...@mnc.ch
An: Andreas Fink af...@list.fink.org
CC: devel Devel devel@kannel.org
Betreff: Re: singlethreaded or multithreaded
Andreas Fink afink 'at' list.fink.org writes
devel@kannel.org
Betreff: Re: singlethreaded or multithreaded
I think you should for sure be able to accept multiple simultaneous
incoming connections as its in the nature of a webserver. If you
process them sequentially or more than one in parallel is then a
performance issue. Kannel
: singlethreaded or multithreaded
I think you should for sure be able to accept multiple simultaneous
incoming connections as its in the nature of a webserver. If you
process them sequentially or more than one in parallel is then a
performance issue. Kannel for sure doesnt stop working until it got
: singlethreaded or multithreaded
Beatrice,
May I ask why are you going to develop a custom web server instead of
using any of the well-proven open source alternatives already available?
Regards,
--
Alejandro Guerrieri
aguerri...@kannel.org
On 06/05/2009, at 17:28, Beatrice
-Nachricht
Datum: Wed, 6 May 2009 17:15:49 +0200
Von: Andreas Fink af...@list.fink.org
An: Beatrice Tamburrino beatrice.tamburr...@gmx.ch
CC: devel Devel devel@kannel.org
Betreff: Re: singlethreaded or multithreaded
I think you should for sure be able to accept multiple simultaneous
Andreas Fink schrieb:
I think you should for sure be able to accept multiple simultaneous
incoming connections as its in the nature of a webserver. If you process
them sequentially or more than one in parallel is then a performance
issue. Kannel for sure doesnt stop working until it got the
On Wed, 2009-05-06 at 17:52, Beatrice Tamburrino wrote:
The webserver should be part of a big software engine which my company
develops. we also use the apache server but for incoming traffic, we need a
custom build one for overviewing the requests.
anyway, its not a big deal to write a
Stipe Tolj st 'at' tolj.org writes:
The HTTP client layer in gwlib/http.[ch] works this way:
We look for a connection to the target host in our connection pool. If we have
one in the pool we grep it and use it, if we don't have one, we create a TCP
connection to the host.
As soon as the
...@mnc.ch
To: Stipe Tolj s...@tolj.org
Cc: devel Devel devel@kannel.org
Sent: Wednesday, May 06, 2009 7:28 PM
Subject: Re: singlethreaded or multithreaded
Stipe Tolj st 'at' tolj.org writes:
The HTTP client layer in gwlib/http.[ch] works this way:
We look for a connection to the target host
13 matches
Mail list logo
