On 24/03/12 02:31, Kingsley Idehen wrote:
On 3/23/12 11:18 AM, Will Daniels wrote:
Hi,
I found an old thread talking about IPv6 support touted for the
commercial Virtuoso product[1]. Does this exist yet?
The special IPv6 features you mention aren't part of any release at the current
time.
Following up on this, I did take a stab at adding ipv6 support in honour of the
World IPv6 Launch on 6th June. I had some initial success but found that my ipv6
connectivity kept dropping off and naturally assumed I had screwed something up
in the code, which I never got around to investigating further.
But I just discovered that it was actually my server host (OVH) who changed some
things on their ipv6 network without notice[1] that was causing the problem, and
my ipv6 virtuoso is actually running fine now.
So I will complete and clean up my patch to publish the changes via github for
anybody who is interested, but I'm unsure about whether to invest time in
figuring out all of the relevant ipv6 details for non-linux platforms because:
1) I don't currently have access to many of the proprietary platforms (Windows,
Mac, HP-UX) supported by virtuoso to test with.
2) I'm not sure how receptive OpenLink is anyway for external contributions, and
what requirements may be attached there (e.g. is there any contributors
agreement like some other open source projects have)?
I'm happy to do the work (so far as I can WRT proprietary platforms) but
obviously it takes much more time to try to do things in ways best suited for a
"proper" contribution, so I would hate to go to all that trouble if OpenLink
doesn't really want it, or isn't likely to take it if it needs some
testing/tweaking for other platforms.
Your advice about that would be appreciated so that I can decide how best to
continue.
Cheers!
-Will
[1] http://web.archiveorange.com/archive/v/RCtW0l4tvxvGxkdhRec6
