: data definition has no type or storage class
gw/smscconn_p.h:215: error: `shutdown' redeclared as different kind of symbol
On Tuesday 20 January 2004 16:07, David Schmitz wrote:
Hi,
attached is a patch implementing some new configuration parameters based
on POSIX regular expressions. All new
Alexander Malysh wrote:
On Friday 23 January 2004 15:16, David Schmitz wrote:
Hi Alex,
well, this means we (e.g. I) should wrap the regex stuff in ifdefs. :(
Expect v3 this afternoon or monday)
not necessary and ifdefs are ugly ;)
Keep quoting me :)
What's about defining
,white-list-regex,black-list-regex
Please try out the patch and drop me a line with your comments :)
--
Mit freundlichen Gruessen/Best regards
David Schmitz
Softwareentwicklung
-
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf
K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H
g2HyLAEKQIp30Q==
=aYCI
-END PGP PUBLIC KEY BLOCK-
--
Mit freundlichen Gruessen/Best regards
David Schmitz
Softwareentwicklung
-
Wapme Systems AG
Vogelsanger Weg 80
Hello list,
attached are two patches for the HTTP-timeout thing. The first one uses
a threaded-approach and the second one works without threads. As some
tests have shown, the threaded version only performs better in high-load
situations, and even then only marginally. Thus, I would like you
created new thread for every outgoing http
request. And even this worked pretty fast.
Alexander Malysh wrote:
hey, factor 50 I want see a patch w/o YAT!!!
It can't be s bad...
On Thursday 27 November 2003 17:24, David Schmitz wrote:
Hi,
your YAT-hatred ;) is well known
when run_status still is limbo.
David Schmitz wrote:
Hi Slava,
no need to vote for my patch, because your approach is better.
IMO the discussion difftime vs. thread is needless, because we should
aim for scalability, and the thread-approach scales
Thus I have merged my client stuff into your
results w/ and w/o YAT, so we can see
how is performance w/o YAT affected?
Thanks in advance...
On Thursday 27 November 2003 15:02, David Schmitz wrote:
Hi list,
attached is the IMHO final version of the timeout-patch. I took the
thread-approach as discussed with Slava (thanks for your
will be called for those clients, wich call
port_put function then and we have panic, because port just doesn't
exists in the dictionary anymore.
On Monday 24 November 2003 13:52, Vjacheslav Chekushin wrote:
--
Mit freundlichen Gruessen/Best regards
David Schmitz
Softwareentwicklung
enviroment this check will be quite undeterminate and can
be not called for hours. Isn't it?
David Schmitz wrote:
Hi again,
attached is the new patch for HTTP-timeouts. I have included the work
of Slava wrt. server-timeouts, but modified it such that no new
thread is needed. Another new thing
time.
So for busy enviroment this check will be quite undeterminate and can
be not called for hours. Isn't it?
David Schmitz wrote:
Hi again,
attached is the new patch for HTTP-timeouts. I have included the
work of Slava wrt. server-timeouts, but modified it such that no
new thread is needed
sane approach.
Please have a look at the patch. If anyone comes up with a better
solution or finds errors/mistakes: I am happy to learn :))).
Mit freundlichen Gruessen/Best regards
David Schmitz
Softwareentwicklung
-
Wapme Systems
,
David
--
Mit freundlichen Gruessen/Best regards
David Schmitz
Softwareentwicklung
-
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf
Tel.: + 49 -211-7 48 45 - 2708
Fax: + 49 -211-80-6-06-2801
E-Mail: [EMAIL PROTECTED]
Internet
13 matches
Mail list logo