On Thu, Aug 11, 2011 at 10:59 AM, Andrew Stitcher <[email protected]> wrote:
> I've been spending much of my time in the past few weeks getting support
> for IPv6 in to the C++ and python code bases, and I expect to get it in
> the code base in the next few days (unless someone can see a problem not
> yet noticed with the code).
>
> I've created an umbrella Jira - QPID-3404 to track IPv6 work with a
> bunch of sub-tasks to track the details.
>
> It'd be great if we can announce full IPv6 support for the 0.14 release:
> Does anyone more qualified than me want to take on the work for the Java
> code base? I'd be happy to advise or even do the work if no one else
> steps forward, but I suspect that someone more familiar with the Java
> code would be better suited.
>
> So I'm really appealing for volunteers for QPID-3408  -
> https://issues.apache.org/jira/browse/QPID-3408
>
> Note that in general there are two issues in IPv6 support that have
> emerged so far:
>
> 1. Actually listening/connecting to IPv6 sockets (including the correct
> reconnect and multiple listening socket logic)

My understanding is that since Java 1.4, there have been support for IPv6.
AFAIK this is transparent and code wise we don't really have to do
anything special.
But of course we have to test this out and see.

>
> 2. Adding literal IPv6 support to any URL parsing.

This is where I suspect we will need some work. The URL parser **may**
fail when we use a IPv6 address.
If it does not, then that would be a real bonus.
I will test this out today and see.

> They are separable and 1 is useful without 2, but 2 is necessary to have
> complete IPv6 support.
>
> Andrew
>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:[email protected]
>
>

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to