Hi!
We create a function which sends a XML over named pipe to a SQL-DB every time the user posts an Order (send with NPipeBusAdapter.dll).
Most of the time it works fine. But when the XML-Stream (large order)becomes to long, then the receive program can not get the xml.
The programmer of the receive program analyses the problem and says that the NPipeBusAdapter.dll sends with blocks:
"start block" "Stream" "end block"
When the stream gets to long the dll sends:
"start block" "stream" "end block" "start block" "stream" end block" .....
They use a MS dll to receive (windows).
I don’t know if this is right because I have no information how the dll do the communication.
Did anybody know how I can get the documentation about this dll and how the communication works.
We have written mails to MS but nobody knows about the Problem and the documentation !
Thanks
0
Comments
The protocol is very similar to what you describe. Basically it is a start byte, length of data and data, and there is also another to describe end of transmision, and another one to describe reply expected.
Unfortunately, I don't think this is oficially documented, but with few messages, it is possible to "decode" the protocol.
“This posting is provided "AS IS" with no warranties, and confers no rights.”