Lnet CallAction routine does nothing.
lazarus / 38-Networking and Web Programming

----------------------------------------------------------------------
Andyk · 2012-06-11 10:50

I'm using the non visual version of lnet telnet protocol to implement
a blocking textual communication channel to a remote device. So I
implement a higher level  loop to wait until an EOL is detected in the
on receive event but the on receive event never gets fired in this
mode.

If I write the command without starting a read loop, then the on
receive event fires and I can see the return string in the debugger.

So my guess is without the visual framework the eventer does not get
called.

I read that the CallAction function needs to be called in the loop if
nonvisual version is used, so I included this call in the loop but
still no onreceive event gets fired.

When I debug traced the call into CallAction it just ends up with

function TLEventer.CallAction: Boolean;
begin
  Result := True;
  // override in ancestor
end;

So basically, the CallAction routine does nothing.

Am I doing something wrong here, or is this version of lnet faulty
(0.6.5) ?

----------------------------------------------------------------------
Andyk · 2012-06-11 20:47

I managed to get this to work.

Don't copy the examples and create your own eventer, the telnet
protocol creates its own eventer on connect if one has not already
been assigned and that ones Callaction routine works.

----------------------------------------------------------------------
Almindor · 2012-07-11 00:19

Yes, this is the behavior for all lNet components, otherwise they
couldn't work unless you manually create the eventer.

The option is given tho, so you can save processing power on the
eventer calls and have multiple components in one thread/process (but
you need to assign the eventer before activating the connection on the
components).