-----BEGIN PGP SIGNED MESSAGE-----
On Fri, 29 Dec 2000, Paul Rony wrote:
> I'm trying to follow the Appendix C in order to write my own client for
> Windows NT. I'm using C++, so I'm in full control of every byte sent and
> received. My problem is that the documentation does not clearly define all
> bytes in and out.
Yes it's true, you will need to reverse engineer the perl code.
> For example, the Data Exchange section mentions that all data must be
> prepended with the length of the string. Is this length a 16-bit or 32-bit
> number? Why is this length needed when the XCP protocol already includes a
> Content-Length header on the first line?
This is most likely a legasy issue from the earlier API.
The number is an unsigned short.
> Paul Rony
> Merchantware
>
- -----------------------------------
Dont worry Marge.
Trying is the first step to failure
-- Homer J. Simpson
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
Comment: Public key ID: 0xD467B527
iQEVAwUBOkzp41j6i6zUZ7UnAQH0rwf/QbAPjccuv5QfhjFkIxAdzniEuWrscNSt
iS1/3GqC4CAcepfS/hgg+gg0t2hAZAwYD6py4ENDRhNUpTrbVLNgmB23mGDbiONe
dONMCYEKYMC+/uZXh9dEMPMGi363LkMZt6+roC5C9KZCiDBtDpMnAVxf4YNfLkjx
QE+Z1LS6m/1MfHia3BXjUjKk8QAa+jHkjGcz9XxTpZGyyhiiAY+jdExEEBnSKjiu
I/K/f1P+svg5+rSZag/lAGzFVZHoaL4yvskKciXDHUSJihFzLiJIQsYo05EEQQde
SdCrx+NcUgsTWdAD2FZjZC7QMsCCyL2D83p3J/ubjUyGrZ+XwAcVSg==
=yqSw
-----END PGP SIGNATURE-----
