Jarek,
Ah right the protocol limitation, I didn't think of that. What is the use
of discarding a message or throwing an error? I would simply have the
target automatically split if size > 65000.
Of course what you propose is a nice feature but personally I don't see a
use for it.
Thanks for your amazingly fast response,
Francis
-----Original Message-----
From: Jaroslaw Kowalski [mailto:
jaak@...]
Sent: Friday, September 15, 2006 14:47
To: Francis Gingras
Cc:
nlog-list@...
Subject: Re: [Nlog-list] TCP target buffer overload
Francis Gingras wrote:
> Hi,
>
> When sending a large string (68000 characters) to a TCP target I get
> this exception. I am using NLOG (.NET 2.0) v. 0.95 (I think, it shows
> 1.0.0 but that can't right).
>
That's the limitation of the protocol. UDP Cannot be used to send more than
2^16 bytes in one packet. What should we do about it?
There are 3 options:
* quietly discard the message
* throw an error
* split the message into smaller pieces.
I propose the following attributes be added to the Network target:
maxChunkSize (default = 65000)
bufferOverflowAction=Discard|Error|Split
What do you think? If we are quick, I believe I can add them before 1.0
ships.
Jarek
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642_______________________________________________
Nlog-list mailing list
Nlog-list@...
https://lists.sourceforge.net/lists/listinfo/nlog-list