Menu

#127 Lookup constructor with resolver parameter

None
closed
nobody
None
5
2019-05-18
2015-03-15
No

I think it would be good to have a Lookup constructor with the resolver as parameter. If you what to use a own resolver this would avoid to set it seperatly.

Discussion

  • Brian Wellington

    Setting it separately is a single, trivial call to Lookup.setResolver() for each query. If you want to use a custom resolver for all queries, it's a single call to Lookup.setDefaultResolver() that's not per-query.

    Using a different resolver for a single query is not common enough or important enough to warrant a custom constructor.

     
  • Brian Wellington

    • status: open --> wont-fix
    • Group: -->
     
  • Ingo

    Ingo - 2019-05-18

    Ticket moved from /p/dnsjava/feature-requests/20/

     
  • Ingo

    Ingo - 2019-05-18
    • Status: wont-fix --> closed
     
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.