To me, it sounds like option 4 of using IPV4 mapped to IPV6 is the cleanest
way to implement this. I'm wondering if we might want to take the approach
used with oodialog and separate the rxsock library from the interpreter
release. The Windows installer could then check the prereqs to ensure it
While I like option 4 there are some things that need to be checked out.
For instance, will this option work when there is no set up for IPv6 on
the adapter? So far I have not been able to determine that from anything
I have read. I am sure there are some other things to check out as well.
As to
David Ashley wrote:
1. As always, the Windows implementation of IPv6 will cause us some
pain. We really need to use the latest version of .Net
IPv6 within Windows does not have a native C/C++ interface, only .Net?
Blessings,
--
Michael Lueck
Lueck Data Systems
