hi, <br><br>thankx for your help .. i will use the same in set function. <br><span class="gmail_quote"></span><br><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I think a potential problem is that some functions, such as the set<br>function relied upon by the ctor modified below, are intended to let the<br>OS make the IPv4/IPv6 call if AF_UNSPEC is passed as the address family.<br>
By using determine_type() to specify AF_INET or AF_INET6, we might end<br>up forcing something into an incorrect family. For example, we are<br>setting up an ACE_INET_Addr to contain the address of an external host<br>that really does not have IPv6, but with the local configuration,
<br>determine_type() returns AF_INET6, then set() will fail because the<br>foreign address that should become IPv4 instead yields IPv6.<br><br></blockquote></div>cant really understand the problem you are talking about ! it would of great help if can 'expand it a bit'.
<br><br>will there be any problem if i make this change in ACE_INET_Addr::set function, if that is the case i have <br>to look for a different solution, as it is critical "i don't break" any functionality by making changes without understanding
<br>the effect of it !!!!<br><br>regards,<br>Prem<br><br>