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 answer from the webserver as its written asynchronously. So it can
have multiple parallel requests to multiple servers (this happens
especially during WAP use). I'm not 100% sure how it handles requests
to the same server as there it can keep a connection open and reuse it
(HTTP Keepalive) but it for sure would not hurt your software to be
able to handle a few requests in parallel as it would give you speed.
On 06.05.2009, at 16:30, Beatrice Tamburrino wrote:
Hi,
I am writing a little webserver for an extern application, this
webserver should handle the incoming http request which kannel calls
with the dlr-url given.
Now, the question is, if kannel forwards the http request
sequentiel, i won't need to take care of the multithreaded stuff..
well, I took a look at the source code but i wasn't able to find
something..
-------- Original-Nachricht --------
Datum: Wed, 6 May 2009 16:23:54 +0200
Von: Andreas Fink <[email protected]>
An: Beatrice Tamburrino <[email protected]>
CC: devel Devel <[email protected]>
Betreff: Re: 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? or pararell
multithreaded??
xox
bea
--
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit
allen: http://www.gmx.net/de/go/multimessenger01
--
Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate +
Telefonanschluss für nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a
