Sorry about the terminology confusion. In client/server programming,
the convention is that the client is the object that initiates the
connection. In .Net remoting, the conventional terminology is that you
have an object that 'sources' data, and an object that 'sinks' data. In
this case, th
Thanks again for your help. But now I am at a bit of a loss. If the sink
class on the server side or on the client? I assume it was on the client
side, but as per you code it appears to be on the server side.
Also, I notice that you are not using the same pattern I use to log events.
I just use t
I did not alter the connection functionality at all. I simply added a
timer: to the log4net 1.2.10 RemotingAppender as follows:
public class TimedRemotingAppender : RemotingAppender
{
public TimedRemotingAppender()
{
FlushPeriod = 10; // seconds
timer = n
Thanks Loren. However, it still doesn't work. I looked into the source for
the remote appender and at no point I see the channel registration. What is
version of log4net ar you using? When you sub-classes the appender, did you
handle the .net remoting connection (channel services and remoting
conf
With a buffer of 95, you won't see anything on the remote appender until
95 log events have been queued. I ended up subclassing the appender to
add a timer to flush automatically every N seconds. Try setting the
buffer length down to 1 or disable it entirely.
~Loren
ppden wrote:
Greetings
