Ryan Hoegg <[EMAIL PROTECTED]> writes: > Daniel Rall wrote: > > >Ryan Hoegg <[EMAIL PROTECTED]> writes: > > > >>You might be interested in the Commons Discovery project, which > >>provides a standard (?) way to find implementations of a given > >>interface. I am going to look into this as a possibility for > >>streamlining the new XmlRpcTransport interface code I am working on > >>with Andrew Evers. > >> > >> > >>Project: http://jakarta.apache.org/commons/discovery.html > >> > >>Good place to get a quick and dirty idea of what this stuff does: > >>>http://jakarta.apache.org/commons/discovery/apidocs/org/apache/commons/discovery/DiscoverClass.html > > >Would this dependency only be necessary on the server side, or would > >it be a requirement on the client side as well? > > You have to forgive me, I spend most of my time programming larger > applications where footprint isn't as much of an issue as with > libraries such as this :)
Tell me about it. SourceCast is freakin' HUGE -- currently 924 MB for a built source tree. Perhaps that gives you guys an indication of where all my time is going. ;) > The JAR for 0.1 is 62K. IMHO, every little bit matters on the applet side. Last time we polled, it seemed we had enough users that it was worth still supporting that use case. > As far as I can tell this dependency would be introduced anywhere we > want to automatically discover an implementation class for an > interface. We could break it off into an AutoDiscoverFactory class > that sits in another package. The reason I bring it up is that > automatic discovery of classes provides a clean way to provide a > default implementation while providing flexibility to the end user for > specifying alternate implementations for an interface. Definitely useful, but IMHO not worth 62k on the applet side. -- Daniel Rall <[EMAIL PROTECTED]>
