This group is intended more to discuss the development of the OAuth protocol rather than anything related to OpenSocial in particular. I recommend that you try your query on one of the OpenSocial lists:
http://groups.google.com/group/opensocial-and-gadgets-spec/topics ...except that I see that you've already done that, so I'd continue pursuing this topic there: http://groups.google.com/group/opensocial-and-gadgets-spec/browse_thread/thread/1380e3daf5654b0c# Chris On Thu, Dec 11, 2008 at 9:15 AM, Hertzel <[email protected]> wrote: > > Hi > > We have investigated a while the OAuth & OpenSocial/Shindig projects, > actually reviewed every piece of documentation and specification about > these technologies including design/best practices, installed the open- > source references (shindig, google-oauth, etc.) > > We have a "ACTIVITY CENTRIC" product with some social features based > on J2EE as server-side and Adobe AIR (RIA) as client-side. > Now, we are intended to socialize our product and would like to get > your advice and recommendations, before start-coding. > > (1) Our requirements are as follow: > (1.1) Exposing our data and services to the community, developers > (1.2) Developing our opensocial gadgets to be installed on existing > opensocial networks > (1.3) providing a new opensocial network based on our current services > > (2) As of our understanding these requirements' implementations > should be as following accordingly: > (2.1) 'RESTify' our services and secure them by GOOGLE-OAUTH SERVER, > implemented & deployed locally + registration module which provides > consumer key & secrets to social consumers > (2.2) Developing gadgets based on opensoial-gadgets which consume our > services from (2.1) - no server is required here beside a web server > hosting the gadgets' xml > (2.3) Deploying the Shindig (java project) container, enhanced by data > server (beside xml) > > > (3) Other question: > (3.1) How could we feed the opensocial activity streams in any > opensocial network by our activities which have been produced in our > product by the viewer? > (3.2) What's your recommendations about mashup gadgets which provide > services/data - from our product + other social sites - in the same > gadget > As of unclear documentation about implimentation of (google) OAuth > Servers (for service providers) & Container servers, we would be much > appreciated to get some advice/directions and best practices beside > what already published on the web! > > Hertzel > > > Hertzel Karbasi Enterprise Architect OPTinity eSolutions, CEO > [email protected] +972.54.431.431.9 MeadoWare is Coming soon! > > > > -- Chris Messina Citizen-Participant & Open Technology Advocate-at-Large factoryjoe.com # diso-project.org citizenagency.com # vidoop.com This email is: [ ] bloggable [X] ask first [ ] private --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
