I doubt that people notice how many Handles they can resolve per second, but it gives a big negative feeling to see that it takes minutes to resolve ONE Handle because of firewalls.
So my opinion is that the plugin default should be HTTP even if that reduces maximum speed as estimated by you from 20 to two Handles resolved per second...
Security is always improved using the native resolution protocol because
it avoids the possibility of DNS cache poisoning, DNS messages spoofing,
and general interference with the non-SSL hdl.handle.net or dx.doi.org
Interesting point. How does performance of "signed native protocol" compare to "HTTP via SSL" proxy based resolution?
You can let the proxy server name point to several servers for load balancing and fail-over, and the plugin could know a number of proxy servers to have alternatives if one fails.
If there will be a config interface, it can also be used to enable UDP resolution manually - or even in a scripted way for those who do mass-installs of Firefox... Having config interfaces, even GUI ones, is common for Firefox plugins.
Cheers, Sean
_______________________________________________ Handle-Info mailing list Handle-Info@cnri.reston.va.us http://www.handle.net/mailman/listinfo/handle-info