This is very cool to hear Matteo! I will definitely have to take a look at your code. It would be nice to integrate some of this into MINA.
-Mike Matteo Merli wrote: > Hi, > > I've started an asyncronous DNS client based on MINA for my HTTP > caching proxy (also based on MINA: > http://alijo.googlecode.com ) > > The client is based on the code from the DNS server in Apache Directory. > > The implementations is not complete yes as : > > * Only returns first IP address in the DNS reply > * Only uses first DNS server (primary), as read from /etc/resolv.conf > * Can cache DNS addresses, but.. caches forever as no expiration is applied > * Does not use aliases > > I plan to work more on the DNS client. If anyone is interested, the > sources can be found here: > > DNS Codec: > http://alijo.googlecode.com/svn/trunk/protocol-dns/ > > DNS Client: > http://alijo.googlecode.com/svn/trunk/alijo/src/main/java/org/mm/proxycache/dns/ > > Again, the code is not polished , but if there is interest I can work > onrefining it and extracting it in a decent form. > > Regards, > Matteo > <[EMAIL PROTECTED]> > > On Feb 12, 2008 3:59 PM, Eero Nevalainen <[EMAIL PROTECTED]> wrote: >> Btw, what was the status of DNS resolution in MINA? I remember that at >> some point DNS resolving used the blocking java API calls. I could >> imagine that an asynchronous HTTP-client would have to perform a lot of >> DNS queries(or not, depending on use). Could this become a pithole? >> >> -Eero >> >> >> Rick McGuire wrote: >>> The one feature I like about the AHC client that appears to be missing >>> here is the higher-level abstraction of an HTTP request. The one >>> drawback of doing everything with URLs is the requirement that the user >>> of the client needs to be responsible for encoding all of the parameter >>> information in the URL. In the AHC approach, a request is configured as >>> an operation to a particular address and additional specifics of the >>> operation are attached to the request (parameters, credentials needed >>> for authentication, proxy configuration etc.). The AHC client then uses >>> that information to handle the URL encoding, authentication challenges, >>> proxy connection, etc. There are times where a straighforward "fetch me >>> this URL mode" is sufficient. There are other situations where that >>> becomes awkward to use. >>> >>> Rick >>> >>> Mike Heath wrote: >>>> I posted some use cases here: >>>> http://cwiki.apache.org/confluence/display/AWEB/ClientUseCases They >>>> still need some refinement to properly convey what I want but they're a >>>> decent start. >>>> >>>> I've also posted a hypothetical AsyncWeb Client API at >>>> http://swamp.homelinux.net/mina/asyncweb/client/api/ with the intent to >>>> further promote discussion and foster more innovative ideas. I would >>>> love to here some feedback on this API. What do you like, dislike, not >>>> understand? Where do you see room for improvement? The API is really >>>> rough in places but for the most part it conveys the ideas I've had over >>>> the past week or so. Any suggestions for name changes to classes and/or >>>> methods are welcome. >>>> >>>> -Mike >>>> >>>> >> > > >
