🚀 go-pugleaf

"Paul at NCF" <notplmacca@clara.co.uk> wrote in message
news:46c70d07$1@newsgroups.borland.com...

> I had to remove include lines for AntiFreeze headers

Please be more specific.  What exactly did you remove, and from where
exactly?

> The server and client test harnesses are working (including
> receiving SysLog data from my wireless ADSL router),
> however I notice a difference in behaviour for two different
> send calls.

What calls are you referring to exactly?  Where are you seeing the data
appear?  Again, you need to be more specific.

> With SysLog Client rebuilt only (and using Indy9 Server) the
> data received is:

Since there is no such output being generated by Indy, I have to assume that
you are formatting the message data into your own string value.  Please show
your actual code so we can see what fields you are using.

> This send leaves the host name blank:

You are not assigning anything to the TIdSysLogMessage::Hostname property in
your code.  Looking at the source code for TIdSysLogMessage, I see that it
tries to assign a default value to that property inside of the
TIdSysLogMessage::InitComponent() method.  However, something I observed
last week was that the InitComponent() method is not always called correctly
under C++.  I have no idea why yet.

> UDP Client & Server Components, I get the following compile errors.
> Have all these interfaces changed?

Yes, which you can see if you look at the declarations in the header files.

The send/receive methods need some explanation.  You can't pass raw memory
buffers to Indy anymore, mainly due to the .NET support.  In this particular
case, you will have to wrap your data into a TIdBytes.  For sending data,
you can use RawToBytes().  For receiving data, you can use BytesToRaw().
For example:

    IdUDPClient->SendBuffer(RawToBytes(Udata, Ulength));

    TIdBytes buf;
    buf.Length = DataSize;
    DataSize = IdUDPClient->ReceiveBuffer(buf, Wait);
    BytesToRaw(buf, Data, DataSize);
    RxBuf->Ulength = DataSize;


Gambit