Hey Wolburg ,

The easiest way to do this is by using Shindig, the open source, Open
Social reference implementation: http://incubator.apache.org/shindig/

Now Shindig isn't available in .net, however you can run it next to
  .net, and talk to it through the meta-data service to retrieve
information about gadgets, which you can then use to populate your
gadget gallery's and other UI components, and retrieve the URL's you
can use to construct the gadget iframe's.

There's a simple guide on how to setup (PHP) shindig and an example
container (partuza, which uses the same metadata service) on windows
here: http://www.chabotc.com/generic/setting-up-shindig-and-partuza-on-windows/

And you can see a html/javascript based example (just meant as an
example, normally you would do this server sided and not in html) that
you can inspect using firebug here (check the POST request to /gadgets/
metadata): 
http://modules.partuza.nl/gadgets/files/container/sample-metadata.html

Alternatively you could also go take a look at OpenCampfire.net:
http://code.google.com/p/open-campfire/
Their working on making a .net version of shindig, however they only  
started
development very recently so my guess is it will be a few months  
before they
have a finished version that's ready for production. However if your a  
strong
.net opponent maybe you could help them get it done quicker? :)

Hope that helps you get started!

        -- Chris

On Jul 10, 2008, at 3:43 AM, Wolburg wrote:

>
> We're developing a new social network. Where can we start if we want
> to support this api. For our application.
> The application is in c# .net.
>
> Thanks in advance
> 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Implementing OpenSocial Containers" 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/opensocial-container?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to