There is already a forum thread on this (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=82345&start=0&postdays=postDays&postorder=postOrder&highlight=highlight) and a jira issue (http://jira.jboss.com/jira/browse/JBREM-497).
Although I still perfer to resolve a host name only once (and not per call) I can certainly see there are cases in which delaying the resolution until reaches the client would be beneficial. So the jira issue basically states that if someone configures to use host name, it will be used. However, one of the real problems with this is what to do about the InvokerLocator's equals() method. Currently it compares the hash code of the internal uri value. So if have 'socket://localhost:1234' and 'socket://127.0.0.1:1234' they will not evaluate as being equal. One way to get around this would be to during runtime, check the ip value of the host name and evaluate that way. However this will make things like putting a InvokerLocator in a HashMap very expensive as will have to do a resolution on the host name each time. If have any suggestions on how to solve this problem, will make resolution of this issue come much faster. Thanks. -Tom View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3947217#3947217 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3947217 ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
