Hey,
Indeed OCS and ownCloud seem like the sort of infra we could be using for this. To implement more support usually boils down to adding an "object" or a "document" schema for what you want to store, but my friend Dan here could elaborate on that or refer us to Frank who'd be the authority to ask. For very simple stuff I personally use twisted, and I already started thinking about a way to test clients on the handset or being tested through your desktop devel env against a "mockup" server, this[0] is one example to achieve that where the actual returned data can be easily set. For more content related stuff with out of the box account support etc, I also now use Pyramid[1] which has some very nice things built into it already and is 'pay for what you eat' framework. -Sivan [0]: https://projects.forum.nokia.com/navistore [1]: http://docs.pylonshq.com/pyramid/dev/ On Mon, Jan 3, 2011 at 7:27 PM, Niels Mayer <[email protected]> wrote: > On Sun, Jan 2, 2011 at 1:32 PM, Ville M. Vainio <[email protected]> wrote: >> I wonder whether MeeGo, in addition to being a client OS, could also >> serve as an umbrella project for some open web services? That is, >> "MeeGo" would produce the web service in addition to client code that >> uses the service. In practice, role of "MeeGo" could be funding, >> coordination, promotion of client libraries, technology selection, >> whatever. > > The "services" of which you speak will run "in the cloud," or on > generic hardware, using generic linux distributions that already > support myriad "web services" .... Meego appears focused on mobility, > not the "server"side. It's hard enough to get mobility "right" and > there's also just the hard work of supporting myriad hardware > devices, so I'd be afraid of losing focus and broadening the scope of > MeeGo. > > Various projects exist as umbrellas for such open web services: > http://www.opensocial.org/ > http://shindig.apache.org/overview.html > > What makes sense is to support emerging standards, e.g. OpenID, > OpenSocial, OAuth, in a high-level fashion so as to not need to > reinvent the wheel each time a Meego application needs to make use of > such standards of web interaction. > >> In the perfect world, there would be an independent open source >> project in existence that did this already, but at least I haven't >> heard of one. > > The issue is that there's many to choose from, most of which are > clearly not "the one right way to do things" and are at best > http://en.wikipedia.org/wiki/Worse_is_better solutions... therefore, > it may be a mistake to be "choosing" and "standardizing" anything at > this stage, other than supporting emerging standard protocols ... > > See, for example, the kind of "web services" that a Meego application > needs for implementing YouTube Direct: > http://code.google.com/p/ytd-meego/wiki/CitizenJournalismWithYoutubeDirectForMeego > > And what's needed from the "meego application writers" end is to have > all the necessary subcomponents of "web services" implemented in a > high-level fashion, preferably so that the entire interaction with the > "web service" is entirely in QML and Qt Quick. For example: > JSON RPC: > http://code.google.com/p/ytd-meego/wiki/CitizenJournalismWithYoutubeDirectForMeego#JSON_RPC_in_QML > Authentication and Access control: > http://code.google.com/p/ytd-meego/wiki/CitizenJournalismWithYoutubeDirectForMeego#Authentication_and_Access_Control_in_QML > >> A concrete example would be "MeeGo Live", an equivalent of X-Box Live >> (I don't have X-Box, but the service itself seems to be pretty simple >> to implement from what I've read on the internet). We could have MeeGo >> games storing their savegames on the service, with the user switching >> from one MeeGo device to another and opening the same savegames. In >> the perfect world, there would be an independent open source project >> in existence that did this already, but at least I haven't heard of >> one (snarky answer would be "ftp", of course ;-). > > Oh, so you're talking more at the level of what Google offers as > infrastructure for it's Chrome OS Netbooks? Where the network is the > computer, and the network is down ? :-) > > Well you can use their infrastructure: http://code.google.com/appengine/ > and build your own for your app, e.g. > http://code.google.com/appengine/casestudies.html > > or just run Linux on Amazon's electric cloud > http://aws.amazon.com/amazon-linux-ami/ > or take a standard linux distro (fedora), strip away a bunch of fluff, > stick a box on the internets, and call it a webserver. > > So yes, it could be something as standard as "ftp" or "http" since you > need a protocol on which to run your service. > > In my web-platform of choice, http://xwiki.org , arbitrary web > services can be accomplished quite easily: you > write the web service in Groovy ( http://groovy.codehaus.org ) in a > Xwiki document, and then just access the document over the web.... > http://dev.xwiki.org/xwiki/bin/view/Drafts/XWikiJSONWebServiceKickStart > . > > More elaborate social web services are in development at XWiki, all as > open-source: > http://dev.xwiki.org/xwiki/bin/view/Design/XWikisocial > http://gsoc.myxwiki.org/xwiki/bin/view/Google+Gadget+and+OpenSocial+Integration/Screenshots > http://gsoc.myxwiki.org/xwiki/bin/view/Google+Gadget+and+OpenSocial+Integration/Sources > > -- Niels > http://nielsmayer.com > _______________________________________________ > MeeGo-community mailing list > [email protected] > http://lists.meego.com/listinfo/meego-community > _______________________________________________ MeeGo-community mailing list [email protected] http://lists.meego.com/listinfo/meego-community
