Hi, I've been browsing the Java Shindig code a little, and I was wondering what thought had been put into extension points?
As a specific example, I noticed that the implementation of org.apache.shindig.gadgets.RemoteContentFetcher (org.apache.shindig.gadgets. BasicRemoteContentFetcher) kind of lives up to its name. I have no issues with that, but it appears the kind of thing that people might need to replace (BasicGadgetDataCache is another example of this). If it is agreed this is a reasonable goal, the would it be possible to separate out the org.apache.shindig.gadgets into core classes/interfaces and implementation classes? eg: org.apache.shindig.gadgets.core: GadgetDataCache GadgetFeature GadgetView GadgetSpec GadgetException RemoteContentFetcher org.apache.shindig.gadgets.impl BasicRemoteContentFetcher BasicGadgetDataCache etc. (I understand that GadgetRenderingServlet is currently hardcoded to use those implementation classes - I'm sure many Guicey suggestions for fixing that will Spring to mind...) Regards Nick Lothian [EMAIL PROTECTED] IMPORTANT: This e-mail, including any attachments, may contain private or confidential information. If you think you may not be the intended recipient, or if you have received this e-mail in error, please contact the sender immediately and delete all copies of this e-mail. If you are not the intended recipient, you must not reproduce any part of this e-mail or disclose its contents to any other party. This email represents the views of the individual sender, which do not necessarily reflect those of Education.AU Limited except where the sender expressly states otherwise. It is your responsibility to scan this email and any files transmitted with it for viruses or any other defects. Education.AU Limited will not be liable for any loss, damage or consequence caused directly or indirectly by this email.
