Hey Matt, 2010/4/19 Matt Gilg <[email protected]>: > I could, but if it is true that the purpose of the resolver object is to > resolve a hostname to an address, it would break this functionality. If > this was never supported, it may be worth changing the implementation. I'd > need to hack for a couple minutes to get it to a releasable state, but if > this particular patch is of interest, I can generate it.
It should only resolve hostnames that represent localhost, but it could be used to use the public DNS name of the localhost which resolves to a particular external IP address on which you want to sepcifically listen (instead of 0.0.0.0). Another typical case is to use "localhost" to resolve to 127.0.0.1 to only accept connections from localhost. So yes, I think it should resolve. I was assuming you were using a syntactical variant of the resolve() API or perhaps that we were misusing the boost asio interface... It does sound more like a proper bug in boost::asio or name resolution on your platform ? Regards, koen ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
