3 Replies Latest reply on Sep 24, 2010 10:51 AM by Emanuel Muckenhuber

    NetworkInterfaceBinding and wildcard addresses

    Brian Stansberry Master

      There's a slight problem with NetworkInterfaceService. It has a single field for a NetworkInterface, but a wildcard address is associated with multiple network interfaces. So, some information may be lost.

        • 1. Re: NetworkInterfaceBinding and wildcard addresses
          Emanuel Muckenhuber Master

          Hmm, true. I think the main problem with this is the usage of NetworkInterfaceBinding with multicast addresses, since it uses the NetworkInterface. Maybe we just want to add a isWildcard() and return null for the network interface in this case?

          • 2. Re: NetworkInterfaceBinding and wildcard addresses
            Brian Stansberry Master

            Can NetworkInterfaceBinding return a Set<NetworkInterface> ?

             

            Also, should SocketBinding.createMulticastSocket() be joining the group? Once it has created ManagedMulticastSocketBinding it has performed it's core mission of making sure the socket can be tracked. The caller can be responsible for other tasks, with SocketBinding just being responsible for provided all needed configuration information.

             

            Somewhat related, I opened https://jira.jboss.org/browse/JBAS-8470 . We can deal with that after M1, if needed, as I don't think createMulticastSocket() is actually going to be used in M1.

            • 3. Re: NetworkInterfaceBinding and wildcard addresses
              Emanuel Muckenhuber Master

              Brian Stansberry wrote:

               

              Can NetworkInterfaceBinding return a Set<NetworkInterface> ?

              Sure.

               

              Brian Stansberry wrote:

               

              Also, should SocketBinding.createMulticastSocket() be joining the group? Once it has created ManagedMulticastSocketBinding it has performed it's core mission of making sure the socket can be tracked. The caller can be responsible for other tasks, with SocketBinding just being responsible for provided all needed configuration information.

               

              Somewhat related, I opened https://jira.jboss.org/browse/JBAS-8470 . We can deal with that after M1, if needed, as I don't think createMulticastSocket() is actually going to be used in M1.

              Yeah, maybe just creating ManagedMulticastSocketBinding would make more sense for now. We can review that as part of JBAS-8470 later again.