On Tue, Mar 25, 2008 at 12:54 AM, Martin Webb <[EMAIL PROTECTED]>
wrote:

> >
> > Currently we have servlets in gadgets/http and social/.
> >
> > This doesn't really make any sense -- all the servlets, regardless of
> what
> > data they manipulate, should go in one place. I suggest
> > org.apache.shindig.http or possibly org.apache.shindig.servlets.
> >
> > We can then ensure that we have consistency in the shared details
> between
> > gadget rendering and social data, such as OAuth.
> >
>
> Will it be possible to also extract the servlets out into their own child
> maven project - so that they can be wrapped as a jar and used in both the
> gadget server and in separate gadget container web apps as a maven
> dependency?


I don't really see much point -- the servlets are useless without the code
they depend on. I'd expect the non-servlet stuff to see some re-use (which
is the reason why the servlets are separate to begin with), but I don't see
what good the servlets would do without the core classes.

>
>
> Martin
>



-- 
~Kevin

Reply via email to