On 2 September 2011 11:46, Scott Wilson <[email protected]>wrote:
> On 2 Sep 2011, at 10:34, Ross Gardler wrote: > > > On 2 September 2011 10:17, Jasha Joachimsthal > > <[email protected]> wrote: > >> On 2 September 2011 10:55, Scott Wilson <[email protected] > >wrote: > > > > ... > > > >>>>> For OpenSocial gadgets, can you use a similar process? So package up > the > >>>>> gadget's resources and XML descriptor in a zip and drop it into a > >>> watched > >>>>> location for Rave to unpack and host locally? > >>>>> > >>>>> > >>>> You could build that but why wouldn't you store this information in > the > >>>> database? Then you can do runtime CRUD operations on the widget > through a > >>>> management interface. We can create urls that follow a pattern to > return > >>> the > >>>> widget definition, image etc. > >>>> Just my €0.02 > >>> > >>> The watcher script unpacks the widget, parses the definition and adds > the > >>> metadata to the database. > >>> > >>> That required access to a filesystem location for both the server and > the > >> administrator. > > > > Yes. For a development environment that will always be the case, for a > > live environment one assumes there would be a mechanism for deploying > > the widgets securely, otherwise how would they get there. > > > > We have found that this is the most flexible approach, but there is > > still a form to upload widgets directly to a live server. The key is > > how easy it is for developers on their first deployment. > > We ended up with three deployment mechanisms for widgets: > > - by dropping into to the /deploy folder > - by POSTing to /widgets/ > - by uploading via a web form > > (They all ultimately do the same thing) > Ahh so there are more ways to add a new widget. Thanks for the clarification :)
