You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Aaron Mulder <am...@alumni.princeton.edu> on 2005/08/21 21:06:57 UTC

Management & Ports

	So I'm looking at the concept of network ports in the management 
API.  Normally this seems pretty clear, but there are some "network 
connectors" that don't actually have a port, such as the in-VM transport 
for ActiveMQ.

	It makes me wonder if our standard port properties should be
Integers instead of ints (they're ints and the moment).  But if I look at,
say, java.net.URI, they use an int and say that they'll return -1 if no
port is defined.  That's not as obvious to me, but it works.  Any
thoughts?

Thanks,
	Aaron

Re: Management & Ports

Posted by Matt Hogstrom <ma...@hogstrom.org>.
Alan D. Cabrera wrote:

> Aaron Mulder wrote, On 8/21/2005 12:06 PM:
>
>>     So I'm looking at the concept of network ports in the management 
>> API.  Normally this seems pretty clear, but there are some "network 
>> connectors" that don't actually have a port, such as the in-VM 
>> transport for ActiveMQ.
>>
>>     It makes me wonder if our standard port properties should be
>> Integers instead of ints (they're ints and the moment).  But if I 
>> look at,
>> say, java.net.URI, they use an int and say that they'll return -1 if no
>> port is defined.  That's not as obvious to me, but it works.  Any
>> thoughts?
>>
> Staying with ints that return -1 makes sense to me.

I don't think I'm partial to either but I would prefer a general 
preference for one over the other.  Makes coding a bit more 
predictable.  I'd probably lean toward Integer's, Double's, etc. myself.

>
>
> Regards,
> Alan
>
>
>
>
>
>

Re: Management & Ports

Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
Aaron Mulder wrote, On 8/21/2005 12:06 PM:

>	So I'm looking at the concept of network ports in the management 
>API.  Normally this seems pretty clear, but there are some "network 
>connectors" that don't actually have a port, such as the in-VM transport 
>for ActiveMQ.
>
>	It makes me wonder if our standard port properties should be
>Integers instead of ints (they're ints and the moment).  But if I look at,
>say, java.net.URI, they use an int and say that they'll return -1 if no
>port is defined.  That's not as obvious to me, but it works.  Any
>thoughts?
>
Staying with ints that return -1 makes sense to me.


Regards,
Alan