> The server is a kylix app

Yay!  Another Kylix developer!


> I just changed it like I originally pointed out and everything works fine
now.

This may, or may not, be a confirmation that CodeLongInt() is translating
into Network Byte Order (Big Endian), in opposition to what the rest of the
code is doing and expecting.


> I don't know if I will have time to do more testing.

I definitely DON'T have the time to work on code that's not affecting me
right now... but I keep thinking that if we all helped to tackle these sorts
of problems we'd all have a better library, and wouldn't be bit by these
problems down the road.  (Like Natalie and others' encounters with the
infamous 500 error...)

I don't think we're that far from confirmation of the problem...  If I can,
I might very well throw together some "proof of concept" code when I get
back in a few hours.  I think we're just a few BSWAPs away from proving it's
sending the wrong byte order.

I don't have compilers running on this machine, but working from memory: We
know that the Kylix and Delphi code are running on Little Endian machines by
definition. The integer methods are sending the bytes straight from memory,
so they're going Little Endian. And I'm pretty darn sure that CodeLongInt()
is just creating 4-byte binary string representations of the integers in Big
Endian format in a slightly convoluted way.

Case closed.


> The goal was to get the 4 year old code working and using the integer
methods on both ends worked fine.

Understood. That's why I also suggested the cheap and dirty workaround: so
that you could get it up and running without having to make any changes
within an external library.  By setting the Indy parameter (conditionally
perhaps), you could get the same effect as modifying the library code, by
only modifying your own...   And thus preventing any synchronization
problems with future library upgrades, etc... (having to remember to make
the same change to any upgrades/updates from Synapse, if the code in the
library source doesn't get changed).


Good Luck.




------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
synalist-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/synalist-public

Reply via email to