Hi Lini,

It would be best to direct your questions about using Shindig to the
[EMAIL PROTECTED] mailing list -- that is the group of people
that are best equipped to answer as they are writing the software.

Cheers,
-Dan

On Thu, May 1, 2008 at 11:14 PM, Lini <[EMAIL PROTECTED]> wrote:

>
> Has anyone read through this. I do not require any detailed
> description on each and every point, but someone, those who are
> currently working on shindig, can atleast give a brief about what
> needs to be done to start and what are the functionalities for each,
> the gadget server and container and how is the flow when an
> application url is sent as a request to the gadget server.
>
> If we know the flow of the entire process, then only one can start the
> work. Checking the mailing list wont help as it is for specific
> functions and does not has any single thread which explains the exact
> flow of the process.
>
> The latest PHP shindig has been committed, so atleast now, someone
> from the team working on it can provide a brief on what has been done
> and what remains to be done.
>
> On Apr 3, 5:04 pm, Lini <[EMAIL PROTECTED]> wrote:
> > Hi all
> >
> > I have gone through the posts here as well as the shindig mailing
> > lists, but still I m not clear on how to start with the container.
> >
> > I m developing a site which will host opensocial apps. For this i need
> > to integrate the gadget server in PHP, but the shindig version of PHP
> > gadget server doesnt works well. Has anyone worked on this and can
> > guide me how to start with this?
> >
> > Thanx in advance.
> >
> > Regards
> > Lini
> >
>

--~--~---------~--~----~------------~-------~--~----~
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