Giuseppe Modugno wrote:
I'm sorry for the second email.
I noticed in tcp_output():
/**/* First, check if we are invoked by the TCP input processing//
// code. If so, we do not output anything. Instead, we rely on
the//
// input processing code to call us when input
Giuseppe Modugno wrote:
I'm trying to understand the mechanisms under TCP_WRITE_FLAG_MORE,
tcp_write() and tcp_output(). I'm using raw API.
First of all, I couldn't understand if tcp_output() is useful or not.
Why do you think all the world would call tcp_output() if it's not useful?
I
Il 13/11/2017 21:25, goldsi...@gmx.de ha scritto:
Giuseppe Modugno wrote:
The prototype for SSI callbacks is:
[..]
I don't see any reference to query string parameters. So how to
select the right action?
Sorry for the confusion. This is a mix of resource optimization,
missing documentation
Nikolas Karakotas wrote:
True for not providing enough information.
Deducing wireshark information I can say:
1. Remote host send a Modbus request
2. For whichever reason we don't respond to it as it may have been
lost because of network or Ethernet driver
3. The remote host then re sends the
Hi,
True for not providing enough information.
Deducing wireshark information I can say:
1. Remote host send a Modbus request
2. For whichever reason we don't respond to it as it may have been
lost because of network or Ethernet driver
3. The remote host then re sends the request and we are able
