php shindig - progress report

[Chris Chabot <ch...@xs4all.nl>]

Hey guys,

Since no one likes to hear "it's being worked on" without being able  
to see it, and i now have the first visible workings of a php version  
i thought i'd post a bit of a progress report.

I've been working for the last 7 or 8 days on a php port of the java  
shindig code, I've chosen to follow the structure as closely as  
possible where the language differences allows for it to make  
supporting the same features and having the same behavior easier. Now  
it's been a bit of a challenge, partially because the last time I've  
read any java code is 8 years behind me, and partially since it's a  
huge undertaking to port an entire large feature set and service  
without being able to test it until all the components are done, and  
php being a completely different environment then the java/jetty one.

I've now reached the point where the basic structure is working, and  
it successfully renders the todo.xml gadget into a valid and correct  
gadget.

I'm still working on the js, rpc, proxy and gadget token bits so their  
not included in this, also the remote content gadgets are not  
supported yet (though that will be very quick to follow).

I expect to have those lacking bits done in the near future, and  
combined with a good bit of testing i hope to have a 'patch' ready for  
submission soonish (and i need to formalize the permission to submit  
it under the apache license with my employer, but that is a mere  
formality).

Feature wise it's completely compatible to the java cousin, including  
the 'features', message bundle, etc support and only the GadgetServer,  
web service and caching parts are different from the java version (in  
memory caching for instance couldn't work in a multi process php  
environment), and i think i'll soon add a few more php specific  
optimizations soon to speed the whole thing up a bit as well.

The code i'm using for porting is from feb 14th, i'll evaluate the  
patches that happen in the meantime once i've got everything done,  
since doing both would be to much of a strain progress right now.

A working demo can be seen here:
http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/todo.xml

And the code-so-far for those who are interested in a sneak preview of  
it is here:
http://www.chabotc.com/php-shindig.tar.gz

Please do keep in mind that it's still work in progress, so i know  
there's no gadget container yet, no proxy implementation etc; If you  
just want a fully functional php shindig server, please wait a little  
more since this is nothing but a code preview :)

	-- Chris

Re: php shindig - progress report

[Karim Jouini <ka...@jouini.info>]

OK then i will start testing next week.

I'm working on a social network based on PHP, and really looking forward
about implementing Google OpenSocial API.

Keep us notified about your progress :) and "bon courage" as we say :-)

Karim

2008/2/21, Chris Chabot <ch...@xs4all.nl>:
>
> Yep that falls under the 'php specific optimizations' part, right now
> it re-renders the message bundles, gadget xml's etc ... and there's no
> need too really, serialize + store in cache is a wonderful way to
> bypass most of the expensive operations.
>
> Diskcache is oddly fast in a lot of cases (not surprisingly the linux
> kernel is incredibly good at keeping file access references and using
> memory to cache them based on that) so thats more efficient as a lot
> of people would assume, but for multi server deployment that's not a
> good option, and shared file systems are horrible with locking and
> thus with cache stampeding prevention too.
>
> Anyhow the short of it is, yes thats high on the list of things to
> make (right after proxy/js/rpc servlet porting is done), and i'll
> provide a disk and memcached backend's for it right out of the box.
> (I'll have to do some swaping with my ZendPlatform bits to include APC
> i think, but that should be doable too).
>
>
>         -- Chris
>
>
> On Feb 21, 2008, at 8:24 PM, Kevin Brown wrote:
>
> > You could provide an abstraction here that uses either memcached,
> > apc, or
> > disk-based caching depending on what's available. APC is pretty much
> > guaranteed to be there, and larger orgs would probably want to use
> > memcached.
>
>

Re: php shindig - progress report

[Chris Chabot <ch...@xs4all.nl>]

Yep that falls under the 'php specific optimizations' part, right now  
it re-renders the message bundles, gadget xml's etc ... and there's no  
need too really, serialize + store in cache is a wonderful way to  
bypass most of the expensive operations.

Diskcache is oddly fast in a lot of cases (not surprisingly the linux  
kernel is incredibly good at keeping file access references and using  
memory to cache them based on that) so thats more efficient as a lot  
of people would assume, but for multi server deployment that's not a  
good option, and shared file systems are horrible with locking and  
thus with cache stampeding prevention too.

Anyhow the short of it is, yes thats high on the list of things to  
make (right after proxy/js/rpc servlet porting is done), and i'll  
provide a disk and memcached backend's for it right out of the box.  
(I'll have to do some swaping with my ZendPlatform bits to include APC  
i think, but that should be doable too).

	-- Chris

On Feb 21, 2008, at 8:24 PM, Kevin Brown wrote:

> You could provide an abstraction here that uses either memcached,  
> apc, or
> disk-based caching depending on what's available. APC is pretty much
> guaranteed to be there, and larger orgs would probably want to use
> memcached.

Re: php shindig - progress report

[Chris Chabot <ch...@xs4all.nl>]

Well since it's completely uncharted territory at the moment, reverse  
engineering the java version without to much in the line of  
documentation, i guess the best and currently only way to contribute  
at the moment, is to download the tarball i linked, do a svn checkout  
of the java source, and see what's missing :-)

Currently that would be:
- Proxy service (including token signing requests)
- RPC service
- Js service

after those are done, you could contribute by testing, testing and  
testing, and fixing that comes up short, and seeing where some area's  
of the code might be improved,without deviating from the java  
version's structure and workings to much.

	-- Chris

On Feb 21, 2008, at 9:06 PM, Karim Jouini wrote:

> hey guys !
>
> I want to contribute to the php port, how can I ?
>
> Thanks !
>
> Karim

Re: php shindig - progress report

[Karim Jouini <ka...@jouini.info>]

hey guys !

I want to contribute to the php port, how can I ?

Thanks !

Karim

2008/2/21, Kevin Brown <et...@google.com>:
>
> On Thu, Feb 21, 2008 at 4:30 AM, Chris Chabot <ch...@xs4all.nl> wrote:
>
>
> > Hey guys,
> >
> > Since no one likes to hear "it's being worked on" without being able
> > to see it, and i now have the first visible workings of a php version
> > i thought i'd post a bit of a progress report.
> >
> > I've been working for the last 7 or 8 days on a php port of the java
> > shindig code, I've chosen to follow the structure as closely as
> > possible where the language differences allows for it to make
> > supporting the same features and having the same behavior easier. Now
> > it's been a bit of a challenge, partially because the last time I've
> > read any java code is 8 years behind me, and partially since it's a
> > huge undertaking to port an entire large feature set and service
> > without being able to test it until all the components are done, and
> > php being a completely different environment then the java/jetty one.
> >
> > I've now reached the point where the basic structure is working, and
> > it successfully renders the todo.xml gadget into a valid and correct
> > gadget.
> >
> > I'm still working on the js, rpc, proxy and gadget token bits so their
> > not included in this, also the remote content gadgets are not
> > supported yet (though that will be very quick to follow).
> >
> > I expect to have those lacking bits done in the near future, and
> > combined with a good bit of testing i hope to have a 'patch' ready for
> > submission soonish (and i need to formalize the permission to submit
> > it under the apache license with my employer, but that is a mere
> > formality).
> >
> > Feature wise it's completely compatible to the java cousin, including
> > the 'features', message bundle, etc support and only the GadgetServer,
> > web service and caching parts are different from the java version (in
> > memory caching for instance couldn't work in a multi process php
> > environment),
>
>
>
> You could provide an abstraction here that uses either memcached, apc, or
> disk-based caching depending on what's available. APC is pretty much
> guaranteed to be there, and larger orgs would probably want to use
> memcached.
>
>
>
> > and i think i'll soon add a few more php specific
> > optimizations soon to speed the whole thing up a bit as well.
> >
> > The code i'm using for porting is from feb 14th, i'll evaluate the
> > patches that happen in the meantime once i've got everything done,
> > since doing both would be to much of a strain progress right now.
> >
> > A working demo can be seen here:
> >
> >
> http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/todo.xml
> >
> > And the code-so-far for those who are interested in a sneak preview of
> > it is here:
> > http://www.chabotc.com/php-shindig.tar.gz
> >
> > Please do keep in mind that it's still work in progress, so i know
> > there's no gadget container yet, no proxy implementation etc; If you
> > just want a fully functional php shindig server, please wait a little
> > more since this is nothing but a code preview :)
> >
> >        -- Chris
> >
> >
>
>
>
> --
> ~Kevin
>
> If you received this email by mistake, please delete it, cancel your mail
> account, destroy your hard drive, silence any witnesses, and burn down the
> building that you're in.
>

Re: php shindig - progress report

[Kevin Brown <et...@google.com>]

On Thu, Feb 21, 2008 at 4:30 AM, Chris Chabot <ch...@xs4all.nl> wrote:

> Hey guys,
>
> Since no one likes to hear "it's being worked on" without being able
> to see it, and i now have the first visible workings of a php version
> i thought i'd post a bit of a progress report.
>
> I've been working for the last 7 or 8 days on a php port of the java
> shindig code, I've chosen to follow the structure as closely as
> possible where the language differences allows for it to make
> supporting the same features and having the same behavior easier. Now
> it's been a bit of a challenge, partially because the last time I've
> read any java code is 8 years behind me, and partially since it's a
> huge undertaking to port an entire large feature set and service
> without being able to test it until all the components are done, and
> php being a completely different environment then the java/jetty one.
>
> I've now reached the point where the basic structure is working, and
> it successfully renders the todo.xml gadget into a valid and correct
> gadget.
>
> I'm still working on the js, rpc, proxy and gadget token bits so their
> not included in this, also the remote content gadgets are not
> supported yet (though that will be very quick to follow).
>
> I expect to have those lacking bits done in the near future, and
> combined with a good bit of testing i hope to have a 'patch' ready for
> submission soonish (and i need to formalize the permission to submit
> it under the apache license with my employer, but that is a mere
> formality).
>
> Feature wise it's completely compatible to the java cousin, including
> the 'features', message bundle, etc support and only the GadgetServer,
> web service and caching parts are different from the java version (in
> memory caching for instance couldn't work in a multi process php
> environment),


You could provide an abstraction here that uses either memcached, apc, or
disk-based caching depending on what's available. APC is pretty much
guaranteed to be there, and larger orgs would probably want to use
memcached.


> and i think i'll soon add a few more php specific
> optimizations soon to speed the whole thing up a bit as well.
>
> The code i'm using for porting is from feb 14th, i'll evaluate the
> patches that happen in the meantime once i've got everything done,
> since doing both would be to much of a strain progress right now.
>
> A working demo can be seen here:
>
> http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/todo.xml
>
> And the code-so-far for those who are interested in a sneak preview of
> it is here:
> http://www.chabotc.com/php-shindig.tar.gz
>
> Please do keep in mind that it's still work in progress, so i know
> there's no gadget container yet, no proxy implementation etc; If you
> just want a fully functional php shindig server, please wait a little
> more since this is nothing but a code preview :)
>
>        -- Chris
>
>


-- 
~Kevin

If you received this email by mistake, please delete it, cancel your mail
account, destroy your hard drive, silence any witnesses, and burn down the
building that you're in.

RE: php shindig - progress report

[Chris Chabot <ch...@xs4all.nl>]

Hey Cassie,

 

I expect to have a 'feature complete' version done this week, that doesn't
mean that it's bug free and perfect yet, but quite functional and does all
the things the Java Shindig server did February the 14th (the codebase I'm
doing the porting from, I've marked recent developments and I'll chase those
changes down once the base is done). So I think that will probably be the
right time to submit the patch.

 

            -- Chris

 

  _____  

From: doll@google.com [mailto:doll@google.com] On Behalf Of Cassie
Sent: Monday, February 25, 2008 23:20
To: shindig-dev@incubator.apache.org
Cc: Matthew (Chewy) Trewhella; Dan Peterson; Chris Chabot
Subject: Re: php shindig - progress report

 

Hey Chris - because the current php implementation is so out of date it
might be good for you to commit this sooner rather than later. (Even if it
isn't fully functional) Then all these wonderful people who have been
volunteering to help can have something in source control to work with. 

What does everybody else think?
Should Chris post an official patch in a jira issue?

Thanks!

- Cassie



On Mon, Feb 25, 2008 at 1:37 PM, Patrick Chanezon <ch...@gmail.com>
wrote:

Congratulations and thanks for the port Chris.
Chewy and myself are developer advocates with Google.
We have been in touch with many social sites who want to implement
OpenSocial and are written in PHP: I will point them to this thread and some
of them may offer help.
When your code is checked in, it would be good if you could log bugs for
areas that need work, in order to show new commiters on what work is needed
for Shindig PHP.
Don't hesitate to ping us if you need any help.
Chewy is based in Europe and may be able to meet with you face to face if
you want.

P@


On Thu, Feb 21, 2008 at 4:30 AM, Chris Chabot <ch...@xs4all.nl> wrote:

> Hey guys,
>
> Since no one likes to hear "it's being worked on" without being able
> to see it, and i now have the first visible workings of a php version
> i thought i'd post a bit of a progress report.
>
> I've been working for the last 7 or 8 days on a php port of the java
> shindig code, I've chosen to follow the structure as closely as
> possible where the language differences allows for it to make
> supporting the same features and having the same behavior easier. Now
> it's been a bit of a challenge, partially because the last time I've
> read any java code is 8 years behind me, and partially since it's a
> huge undertaking to port an entire large feature set and service
> without being able to test it until all the components are done, and
> php being a completely different environment then the java/jetty one.
>
> I've now reached the point where the basic structure is working, and
> it successfully renders the todo.xml gadget into a valid and correct
> gadget.
>
> I'm still working on the js, rpc, proxy and gadget token bits so their
> not included in this, also the remote content gadgets are not
> supported yet (though that will be very quick to follow).
>
> I expect to have those lacking bits done in the near future, and
> combined with a good bit of testing i hope to have a 'patch' ready for
> submission soonish (and i need to formalize the permission to submit
> it under the apache license with my employer, but that is a mere
> formality).
>
> Feature wise it's completely compatible to the java cousin, including
> the 'features', message bundle, etc support and only the GadgetServer,
> web service and caching parts are different from the java version (in
> memory caching for instance couldn't work in a multi process php
> environment), and i think i'll soon add a few more php specific
> optimizations soon to speed the whole thing up a bit as well.
>
> The code i'm using for porting is from feb 14th, i'll evaluate the
> patches that happen in the meantime once i've got everything done,
> since doing both would be to much of a strain progress right now.
>
> A working demo can be seen here:
>
>
http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/
todo.xml
>
> And the code-so-far for those who are interested in a sneak preview of
> it is here:
> http://www.chabotc.com/php-shindig.tar.gz
>
> Please do keep in mind that it's still work in progress, so i know
> there's no gadget container yet, no proxy implementation etc; If you
> just want a fully functional php shindig server, please wait a little
> more since this is nothing but a code preview :)
>
>        -- Chris
>
>



--
Patrick Chanezon, Google Developer Advocate
http://wordpress.chanezon.com/
http://code.google.com/apis/

 

Re: php shindig - progress report

[Akash Xavier <ak...@gmail.com>]

Yeah,
Even if it is old just commit it. Its anyway way better than having a thing
that does pretty much less work.
If you feel this is going to be the base for further improments, just commit
it

On Tue, Feb 26, 2008 at 3:49 AM, Cassie <do...@apache.org> wrote:

> Hey Chris - because the current php implementation is so out of date it
> might be good for you to commit this sooner rather than later. (Even if it
> isn't fully functional) Then all these wonderful people who have been
> volunteering to help can have something in source control to work with.
>
> What does everybody else think?
> Should Chris post an official patch in a jira issue?
>
> Thanks!
>
> - Cassie
>
>
> On Mon, Feb 25, 2008 at 1:37 PM, Patrick Chanezon <ch...@gmail.com>
> wrote:
>
> > Congratulations and thanks for the port Chris.
> > Chewy and myself are developer advocates with Google.
> > We have been in touch with many social sites who want to implement
> > OpenSocial and are written in PHP: I will point them to this thread and
> > some
> > of them may offer help.
> > When your code is checked in, it would be good if you could log bugs for
> > areas that need work, in order to show new commiters on what work is
> > needed
> > for Shindig PHP.
> > Don't hesitate to ping us if you need any help.
> > Chewy is based in Europe and may be able to meet with you face to face
> if
> > you want.
> >
> > P@
> >
> > On Thu, Feb 21, 2008 at 4:30 AM, Chris Chabot <ch...@xs4all.nl> wrote:
> >
> > > Hey guys,
> > >
> > > Since no one likes to hear "it's being worked on" without being able
> > > to see it, and i now have the first visible workings of a php version
> > > i thought i'd post a bit of a progress report.
> > >
> > > I've been working for the last 7 or 8 days on a php port of the java
> > > shindig code, I've chosen to follow the structure as closely as
> > > possible where the language differences allows for it to make
> > > supporting the same features and having the same behavior easier. Now
> > > it's been a bit of a challenge, partially because the last time I've
> > > read any java code is 8 years behind me, and partially since it's a
> > > huge undertaking to port an entire large feature set and service
> > > without being able to test it until all the components are done, and
> > > php being a completely different environment then the java/jetty one.
> > >
> > > I've now reached the point where the basic structure is working, and
> > > it successfully renders the todo.xml gadget into a valid and correct
> > > gadget.
> > >
> > > I'm still working on the js, rpc, proxy and gadget token bits so their
> > > not included in this, also the remote content gadgets are not
> > > supported yet (though that will be very quick to follow).
> > >
> > > I expect to have those lacking bits done in the near future, and
> > > combined with a good bit of testing i hope to have a 'patch' ready for
> > > submission soonish (and i need to formalize the permission to submit
> > > it under the apache license with my employer, but that is a mere
> > > formality).
> > >
> > > Feature wise it's completely compatible to the java cousin, including
> > > the 'features', message bundle, etc support and only the GadgetServer,
> > > web service and caching parts are different from the java version (in
> > > memory caching for instance couldn't work in a multi process php
> > > environment), and i think i'll soon add a few more php specific
> > > optimizations soon to speed the whole thing up a bit as well.
> > >
> > > The code i'm using for porting is from feb 14th, i'll evaluate the
> > > patches that happen in the meantime once i've got everything done,
> > > since doing both would be to much of a strain progress right now.
> > >
> > > A working demo can be seen here:
> > >
> > >
> >
> http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/todo.xml
> > >
> > > And the code-so-far for those who are interested in a sneak preview of
> > > it is here:
> > > http://www.chabotc.com/php-shindig.tar.gz
> > >
> > > Please do keep in mind that it's still work in progress, so i know
> > > there's no gadget container yet, no proxy implementation etc; If you
> > > just want a fully functional php shindig server, please wait a little
> > > more since this is nothing but a code preview :)
> > >
> > >        -- Chris
> > >
> > >
> >
> >
> > --
> > Patrick Chanezon, Google Developer Advocate
> > http://wordpress.chanezon.com/
> > http://code.google.com/apis/
> >
>



-- 
Akash Xavier
akashmanohar@gmail.com

Re: php shindig - progress report

[Cassie <do...@apache.org>]

Hey Chris - because the current php implementation is so out of date it
might be good for you to commit this sooner rather than later. (Even if it
isn't fully functional) Then all these wonderful people who have been
volunteering to help can have something in source control to work with.

What does everybody else think?
Should Chris post an official patch in a jira issue?

Thanks!

- Cassie


On Mon, Feb 25, 2008 at 1:37 PM, Patrick Chanezon <ch...@gmail.com>
wrote:

> Congratulations and thanks for the port Chris.
> Chewy and myself are developer advocates with Google.
> We have been in touch with many social sites who want to implement
> OpenSocial and are written in PHP: I will point them to this thread and
> some
> of them may offer help.
> When your code is checked in, it would be good if you could log bugs for
> areas that need work, in order to show new commiters on what work is
> needed
> for Shindig PHP.
> Don't hesitate to ping us if you need any help.
> Chewy is based in Europe and may be able to meet with you face to face if
> you want.
>
> P@
>
> On Thu, Feb 21, 2008 at 4:30 AM, Chris Chabot <ch...@xs4all.nl> wrote:
>
> > Hey guys,
> >
> > Since no one likes to hear "it's being worked on" without being able
> > to see it, and i now have the first visible workings of a php version
> > i thought i'd post a bit of a progress report.
> >
> > I've been working for the last 7 or 8 days on a php port of the java
> > shindig code, I've chosen to follow the structure as closely as
> > possible where the language differences allows for it to make
> > supporting the same features and having the same behavior easier. Now
> > it's been a bit of a challenge, partially because the last time I've
> > read any java code is 8 years behind me, and partially since it's a
> > huge undertaking to port an entire large feature set and service
> > without being able to test it until all the components are done, and
> > php being a completely different environment then the java/jetty one.
> >
> > I've now reached the point where the basic structure is working, and
> > it successfully renders the todo.xml gadget into a valid and correct
> > gadget.
> >
> > I'm still working on the js, rpc, proxy and gadget token bits so their
> > not included in this, also the remote content gadgets are not
> > supported yet (though that will be very quick to follow).
> >
> > I expect to have those lacking bits done in the near future, and
> > combined with a good bit of testing i hope to have a 'patch' ready for
> > submission soonish (and i need to formalize the permission to submit
> > it under the apache license with my employer, but that is a mere
> > formality).
> >
> > Feature wise it's completely compatible to the java cousin, including
> > the 'features', message bundle, etc support and only the GadgetServer,
> > web service and caching parts are different from the java version (in
> > memory caching for instance couldn't work in a multi process php
> > environment), and i think i'll soon add a few more php specific
> > optimizations soon to speed the whole thing up a bit as well.
> >
> > The code i'm using for porting is from feb 14th, i'll evaluate the
> > patches that happen in the meantime once i've got everything done,
> > since doing both would be to much of a strain progress right now.
> >
> > A working demo can be seen here:
> >
> >
> http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/todo.xml
> >
> > And the code-so-far for those who are interested in a sneak preview of
> > it is here:
> > http://www.chabotc.com/php-shindig.tar.gz
> >
> > Please do keep in mind that it's still work in progress, so i know
> > there's no gadget container yet, no proxy implementation etc; If you
> > just want a fully functional php shindig server, please wait a little
> > more since this is nothing but a code preview :)
> >
> >        -- Chris
> >
> >
>
>
> --
> Patrick Chanezon, Google Developer Advocate
> http://wordpress.chanezon.com/
> http://code.google.com/apis/
>

Re: php shindig - progress report

[Brian McCallister <br...@skife.org>]

Awesome, I am all for replacing the existing... "stuff" !

-Brian

On Mon, Feb 25, 2008 at 6:30 PM, Chris Chabot <ch...@xs4all.nl> wrote:

> Thanks!
>
>
>
> I'm finishing up the proxy and rpc parts this week, once that's done and
> I've been able to validate that everything works as its intended too, I'll
> submit the patch (read: complete new php codebase) for inclusion. Once
> that's accepted I'll start on filing the bugs etc, it'll be nice to get
> this
> rolling and get everyone interested informed and involved!
>
>
>
> Once that's done, it'll become interesting what other OpenSocial sites are
> interested in feature wise so I can take that into account with further
> development, so any information on this topic you can relay to me by that
> time will be quite useful :)
>
>
>
> Chewy, if your ever close to / in the Netherlands, drop me a line ok :)
>
>
>
>            -- Chris
>
>
>
>  _____
>
> From: Patrick Chanezon [mailto:chanezon@gmail.com]
> Sent: Monday, February 25, 2008 22:37
> To: shindig-dev@incubator.apache.org
> Cc: Matthew (Chewy) Trewhella; Dan Peterson; Chris Chabot
> Subject: Re: php shindig - progress report
>
>
>
> Congratulations and thanks for the port Chris.
> Chewy and myself are developer advocates with Google.
> We have been in touch with many social sites who want to implement
> OpenSocial and are written in PHP: I will point them to this thread and
> some
> of them may offer help.
> When your code is checked in, it would be good if you could log bugs for
> areas that need work, in order to show new commiters on what work is
> needed
> for Shindig PHP.
> Don't hesitate to ping us if you need any help.
> Chewy is based in Europe and may be able to meet with you face to face if
> you want.
>
> P@
>
> On Thu, Feb 21, 2008 at 4:30 AM, Chris Chabot <ch...@xs4all.nl> wrote:
>
> Hey guys,
>
> Since no one likes to hear "it's being worked on" without being able
> to see it, and i now have the first visible workings of a php version
> i thought i'd post a bit of a progress report.
>
> I've been working for the last 7 or 8 days on a php port of the java
> shindig code, I've chosen to follow the structure as closely as
> possible where the language differences allows for it to make
> supporting the same features and having the same behavior easier. Now
> it's been a bit of a challenge, partially because the last time I've
> read any java code is 8 years behind me, and partially since it's a
> huge undertaking to port an entire large feature set and service
> without being able to test it until all the components are done, and
> php being a completely different environment then the java/jetty one.
>
> I've now reached the point where the basic structure is working, and
> it successfully renders the todo.xml gadget into a valid and correct
> gadget.
>
> I'm still working on the js, rpc, proxy and gadget token bits so their
> not included in this, also the remote content gadgets are not
> supported yet (though that will be very quick to follow).
>
> I expect to have those lacking bits done in the near future, and
> combined with a good bit of testing i hope to have a 'patch' ready for
> submission soonish (and i need to formalize the permission to submit
> it under the apache license with my employer, but that is a mere
> formality).
>
> Feature wise it's completely compatible to the java cousin, including
> the 'features', message bundle, etc support and only the GadgetServer,
> web service and caching parts are different from the java version (in
> memory caching for instance couldn't work in a multi process php
> environment), and i think i'll soon add a few more php specific
> optimizations soon to speed the whole thing up a bit as well.
>
> The code i'm using for porting is from feb 14th, i'll evaluate the
> patches that happen in the meantime once i've got everything done,
> since doing both would be to much of a strain progress right now.
>
> A working demo can be seen here:
>
> http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/
> todo.xml<http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/todo.xml>
>
> And the code-so-far for those who are interested in a sneak preview of
> it is here:
> http://www.chabotc.com/php-shindig.tar.gz
>
> Please do keep in mind that it's still work in progress, so i know
> there's no gadget container yet, no proxy implementation etc; If you
> just want a fully functional php shindig server, please wait a little
> more since this is nothing but a code preview :)
>
>       -- Chris
>
>
>
>
> --
> Patrick Chanezon, Google Developer Advocate
> http://wordpress.chanezon.com/
> http://code.google.com/apis/
>
>

RE: php shindig - progress report

[Chris Chabot <ch...@xs4all.nl>]

Thanks!

 

I'm finishing up the proxy and rpc parts this week, once that's done and
I've been able to validate that everything works as its intended too, I'll
submit the patch (read: complete new php codebase) for inclusion. Once
that's accepted I'll start on filing the bugs etc, it'll be nice to get this
rolling and get everyone interested informed and involved!

 

Once that's done, it'll become interesting what other OpenSocial sites are
interested in feature wise so I can take that into account with further
development, so any information on this topic you can relay to me by that
time will be quite useful :)

 

Chewy, if your ever close to / in the Netherlands, drop me a line ok :)

 

            -- Chris

 

  _____  

From: Patrick Chanezon [mailto:chanezon@gmail.com] 
Sent: Monday, February 25, 2008 22:37
To: shindig-dev@incubator.apache.org
Cc: Matthew (Chewy) Trewhella; Dan Peterson; Chris Chabot
Subject: Re: php shindig - progress report

 

Congratulations and thanks for the port Chris.
Chewy and myself are developer advocates with Google.
We have been in touch with many social sites who want to implement
OpenSocial and are written in PHP: I will point them to this thread and some
of them may offer help.
When your code is checked in, it would be good if you could log bugs for
areas that need work, in order to show new commiters on what work is needed
for Shindig PHP.
Don't hesitate to ping us if you need any help.
Chewy is based in Europe and may be able to meet with you face to face if
you want.

P@

On Thu, Feb 21, 2008 at 4:30 AM, Chris Chabot <ch...@xs4all.nl> wrote:

Hey guys,

Since no one likes to hear "it's being worked on" without being able
to see it, and i now have the first visible workings of a php version
i thought i'd post a bit of a progress report.

I've been working for the last 7 or 8 days on a php port of the java
shindig code, I've chosen to follow the structure as closely as
possible where the language differences allows for it to make
supporting the same features and having the same behavior easier. Now
it's been a bit of a challenge, partially because the last time I've
read any java code is 8 years behind me, and partially since it's a
huge undertaking to port an entire large feature set and service
without being able to test it until all the components are done, and
php being a completely different environment then the java/jetty one.

I've now reached the point where the basic structure is working, and
it successfully renders the todo.xml gadget into a valid and correct
gadget.

I'm still working on the js, rpc, proxy and gadget token bits so their
not included in this, also the remote content gadgets are not
supported yet (though that will be very quick to follow).

I expect to have those lacking bits done in the near future, and
combined with a good bit of testing i hope to have a 'patch' ready for
submission soonish (and i need to formalize the permission to submit
it under the apache license with my employer, but that is a mere
formality).

Feature wise it's completely compatible to the java cousin, including
the 'features', message bundle, etc support and only the GadgetServer,
web service and caching parts are different from the java version (in
memory caching for instance couldn't work in a multi process php
environment), and i think i'll soon add a few more php specific
optimizations soon to speed the whole thing up a bit as well.

The code i'm using for porting is from feb 14th, i'll evaluate the
patches that happen in the meantime once i've got everything done,
since doing both would be to much of a strain progress right now.

A working demo can be seen here:
http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/
todo.xml

And the code-so-far for those who are interested in a sneak preview of
it is here:
http://www.chabotc.com/php-shindig.tar.gz

Please do keep in mind that it's still work in progress, so i know
there's no gadget container yet, no proxy implementation etc; If you
just want a fully functional php shindig server, please wait a little
more since this is nothing but a code preview :)

       -- Chris




-- 
Patrick Chanezon, Google Developer Advocate 
http://wordpress.chanezon.com/
http://code.google.com/apis/ 

Re: php shindig - progress report

[Patrick Chanezon <ch...@gmail.com>]

Congratulations and thanks for the port Chris.
Chewy and myself are developer advocates with Google.
We have been in touch with many social sites who want to implement
OpenSocial and are written in PHP: I will point them to this thread and some
of them may offer help.
When your code is checked in, it would be good if you could log bugs for
areas that need work, in order to show new commiters on what work is needed
for Shindig PHP.
Don't hesitate to ping us if you need any help.
Chewy is based in Europe and may be able to meet with you face to face if
you want.

P@

On Thu, Feb 21, 2008 at 4:30 AM, Chris Chabot <ch...@xs4all.nl> wrote:

> Hey guys,
>
> Since no one likes to hear "it's being worked on" without being able
> to see it, and i now have the first visible workings of a php version
> i thought i'd post a bit of a progress report.
>
> I've been working for the last 7 or 8 days on a php port of the java
> shindig code, I've chosen to follow the structure as closely as
> possible where the language differences allows for it to make
> supporting the same features and having the same behavior easier. Now
> it's been a bit of a challenge, partially because the last time I've
> read any java code is 8 years behind me, and partially since it's a
> huge undertaking to port an entire large feature set and service
> without being able to test it until all the components are done, and
> php being a completely different environment then the java/jetty one.
>
> I've now reached the point where the basic structure is working, and
> it successfully renders the todo.xml gadget into a valid and correct
> gadget.
>
> I'm still working on the js, rpc, proxy and gadget token bits so their
> not included in this, also the remote content gadgets are not
> supported yet (though that will be very quick to follow).
>
> I expect to have those lacking bits done in the near future, and
> combined with a good bit of testing i hope to have a 'patch' ready for
> submission soonish (and i need to formalize the permission to submit
> it under the apache license with my employer, but that is a mere
> formality).
>
> Feature wise it's completely compatible to the java cousin, including
> the 'features', message bundle, etc support and only the GadgetServer,
> web service and caching parts are different from the java version (in
> memory caching for instance couldn't work in a multi process php
> environment), and i think i'll soon add a few more php specific
> optimizations soon to speed the whole thing up a bit as well.
>
> The code i'm using for porting is from feb 14th, i'll evaluate the
> patches that happen in the meantime once i've got everything done,
> since doing both would be to much of a strain progress right now.
>
> A working demo can be seen here:
>
> http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/todo.xml
>
> And the code-so-far for those who are interested in a sneak preview of
> it is here:
> http://www.chabotc.com/php-shindig.tar.gz
>
> Please do keep in mind that it's still work in progress, so i know
> there's no gadget container yet, no proxy implementation etc; If you
> just want a fully functional php shindig server, please wait a little
> more since this is nothing but a code preview :)
>
>        -- Chris
>
>


-- 
Patrick Chanezon, Google Developer Advocate
http://wordpress.chanezon.com/
http://code.google.com/apis/

Re: php shindig - progress report

[Santiago Gala <sa...@gmail.com>]

El jue, 21-02-2008 a las 09:45 -0800, Cassie escribió:
> So Shindig definitely needs its own tests. The spec will only include
> compliance tests because thats all it can/should enforce. Compliance tests
> will never be equivalent to a regular testing suite because the spec allows
> a lot of different ways to handle one call.
> 

Not to mention that regression tests added because of bugs that are not
spec related would never make into the compliance suite, but are valid
to ensure the same bug does not creep in again.

> It can't test for instance that a person's name field is equal to what you
> think it should be. That could only be in a shindig specific test. The
> compliance test would only make sure that the call returned an
> opensocial.Name object and had at least one field filled out.
> 
> Hope that helps explain things.
> 
> - Cassie
> 
> 
> On Thu, Feb 21, 2008 at 9:15 AM, Bruno Bowden <br...@google.com> wrote:
> 
> > Fantastic Chris. Thanks for the contributions.
> >
> > To help keep the two versions in sync, we should have test cases that can
> > be
> > run against both versions. That's something that belongs with the spec and
> > outside of Shindig.
> >

As said above, compliance tests belong to the spec, but other tests, for
instance in areas where the spec is still not "cooked" or they have been
written to check a bug, they will be shindig specific, or even language
specific (imagine a test that only fails with jdk1.X, or only with a
certain PHP version running the code)

> >
> > On Thu, Feb 21, 2008 at 4:30 AM, Chris Chabot <ch...@xs4all.nl> wrote:
> >
> > > Hey guys,
> > >
> > > Since no one likes to hear "it's being worked on" without being able
> > > to see it, and i now have the first visible workings of a php version
> > > i thought i'd post a bit of a progress report.
> > >
> > > I've been working for the last 7 or 8 days on a php port of the java
> > > shindig code, I've chosen to follow the structure as closely as
> > > possible where the language differences allows for it to make
> > > supporting the same features and having the same behavior easier. Now
> > > it's been a bit of a challenge, partially because the last time I've
> > > read any java code is 8 years behind me, and partially since it's a
> > > huge undertaking to port an entire large feature set and service
> > > without being able to test it until all the components are done, and
> > > php being a completely different environment then the java/jetty one.
> > >
> > > I've now reached the point where the basic structure is working, and
> > > it successfully renders the todo.xml gadget into a valid and correct
> > > gadget.
> > >
> > > I'm still working on the js, rpc, proxy and gadget token bits so their
> > > not included in this, also the remote content gadgets are not
> > > supported yet (though that will be very quick to follow).
> > >
> > > I expect to have those lacking bits done in the near future, and
> > > combined with a good bit of testing i hope to have a 'patch' ready for
> > > submission soonish (and i need to formalize the permission to submit
> > > it under the apache license with my employer, but that is a mere
> > > formality).
> > >
> > > Feature wise it's completely compatible to the java cousin, including
> > > the 'features', message bundle, etc support and only the GadgetServer,
> > > web service and caching parts are different from the java version (in
> > > memory caching for instance couldn't work in a multi process php
> > > environment), and i think i'll soon add a few more php specific
> > > optimizations soon to speed the whole thing up a bit as well.
> > >
> > > The code i'm using for porting is from feb 14th, i'll evaluate the
> > > patches that happen in the meantime once i've got everything done,
> > > since doing both would be to much of a strain progress right now.
> > >
> > > A working demo can be seen here:
> > >
> > >
> > http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/todo.xml
> > >
> > > And the code-so-far for those who are interested in a sneak preview of
> > > it is here:
> > > http://www.chabotc.com/php-shindig.tar.gz
> > >

Cool to see things moving in this front. 

> > > Please do keep in mind that it's still work in progress, so i know
> > > there's no gadget container yet, no proxy implementation etc; If you
> > > just want a fully functional php shindig server, please wait a little
> > > more since this is nothing but a code preview :)
> > >
> > >        -- Chris
> > >
> > >
> >
-- 
Santiago Gala
http://memojo.com/~sgala/blog/

Re: php shindig - progress report

[Dan Peterson <dp...@google.com>]

Cool -- I like that the compliance tests themselves are embedded in a gadget
-- this makes it easy to test on lots of containers. In addition, simply
being able to run the complaince test gadget is a test in and of itself.

-Dan

On Thu, Feb 21, 2008 at 10:09 PM, Cassie <do...@apache.org> wrote:

> ha, and by that link (which ends mistakenly in .js) i really meant:
>
> http://opensocial-resources.googlecode.com/svn/tests/trunk/compliancetests.xml
>
> On Thu, Feb 21, 2008 at 9:53 PM, Cassie <do...@apache.org> wrote:
>
> > btw - the initial compliance tests are here:
> >
> >
> http://opensocial-resources.googlecode.com/svn/tests/trunk/compliancetests.js
> >
> > (these are a wip, any patches are very welcome!)
> >
> > - Cassie
> >
> >
> >
> > On Thu, Feb 21, 2008 at 7:32 PM, Kevin Marks <ke...@gmail.com>
> wrote:
> >
> > > Trying out Cassie's initial spec compliance app which I had to modify
> > > to:
> > > <Require feature="opensocial-samplecontainer"/>
> > > instead of
> > > <Require feature="opensocial-0.7"/>
> > >
> > >  you can see that you're getting there. Presumably not having any
> > > owner info is due to a lack of a real db backend?
> > >
> > > Great progress, looking forward to seeing this soon; we have a lot of
> > > people interested in a fuller PHP version.
> > >
> > > On Thu, Feb 21, 2008 at 9:45 AM, Cassie <do...@apache.org> wrote:
> > > > So Shindig definitely needs its own tests. The spec will only
> include
> > > >  compliance tests because thats all it can/should enforce.
> Compliance
> > > tests
> > > >  will never be equivalent to a regular testing suite because the
> spec
> > > allows
> > > >  a lot of different ways to handle one call.
> > > >
> > > >  It can't test for instance that a person's name field is equal to
> > > what you
> > > >  think it should be. That could only be in a shindig specific test.
> > > The
> > > >  compliance test would only make sure that the call returned an
> > > >  opensocial.Name object and had at least one field filled out.
> > > >
> > > >  Hope that helps explain things.
> > > >
> > > >  - Cassie
> > > >
> > > >
> > > >
> > > >
> > > >  On Thu, Feb 21, 2008 at 9:15 AM, Bruno Bowden <br...@google.com>
> > > wrote:
> > > >
> > > >  > Fantastic Chris. Thanks for the contributions.
> > > >  >
> > > >  > To help keep the two versions in sync, we should have test cases
> > > that can
> > > >  > be
> > > >  > run against both versions. That's something that belongs with the
> > > spec and
> > > >  > outside of Shindig.
> > > >  >
> > > >  >
> > > >  > On Thu, Feb 21, 2008 at 4:30 AM, Chris Chabot <ch...@xs4all.nl>
> > > wrote:
> > > >  >
> > > >  > > Hey guys,
> > > >  > >
> > > >  > > Since no one likes to hear "it's being worked on" without being
> > > able
> > > >  > > to see it, and i now have the first visible workings of a php
> > > version
> > > >  > > i thought i'd post a bit of a progress report.
> > > >  > >
> > > >  > > I've been working for the last 7 or 8 days on a php port of the
> > > java
> > > >  > > shindig code, I've chosen to follow the structure as closely as
> > > >  > > possible where the language differences allows for it to make
> > > >  > > supporting the same features and having the same behavior
> easier.
> > > Now
> > > >  > > it's been a bit of a challenge, partially because the last time
> > > I've
> > > >  > > read any java code is 8 years behind me, and partially since
> it's
> > > a
> > > >  > > huge undertaking to port an entire large feature set and
> service
> > > >  > > without being able to test it until all the components are
> done,
> > > and
> > > >  > > php being a completely different environment then the
> java/jetty
> > > one.
> > > >  > >
> > > >  > > I've now reached the point where the basic structure is
> working,
> > > and
> > > >  > > it successfully renders the todo.xml gadget into a valid and
> > > correct
> > > >  > > gadget.
> > > >  > >
> > > >  > > I'm still working on the js, rpc, proxy and gadget token bits
> so
> > > their
> > > >  > > not included in this, also the remote content gadgets are not
> > > >  > > supported yet (though that will be very quick to follow).
> > > >  > >
> > > >  > > I expect to have those lacking bits done in the near future,
> and
> > > >  > > combined with a good bit of testing i hope to have a 'patch'
> > > ready for
> > > >  > > submission soonish (and i need to formalize the permission to
> > > submit
> > > >  > > it under the apache license with my employer, but that is a
> mere
> > > >  > > formality).
> > > >  > >
> > > >  > > Feature wise it's completely compatible to the java cousin,
> > > including
> > > >  > > the 'features', message bundle, etc support and only the
> > > GadgetServer,
> > > >  > > web service and caching parts are different from the java
> version
> > > (in
> > > >  > > memory caching for instance couldn't work in a multi process
> php
> > > >  > > environment), and i think i'll soon add a few more php specific
> > > >  > > optimizations soon to speed the whole thing up a bit as well.
> > > >  > >
> > > >  > > The code i'm using for porting is from feb 14th, i'll evaluate
> > > the
> > > >  > > patches that happen in the meantime once i've got everything
> > > done,
> > > >  > > since doing both would be to much of a strain progress right
> now.
> > > >  > >
> > > >  > > A working demo can be seen here:
> > > >  > >
> > > >  > >
> > > >  >
> > >
> http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/todo.xml
> > > >  > >
> > > >  > > And the code-so-far for those who are interested in a sneak
> > > preview of
> > > >  > > it is here:
> > > >  > > http://www.chabotc.com/php-shindig.tar.gz
> > > >  > >
> > > >  > > Please do keep in mind that it's still work in progress, so i
> > > know
> > > >  > > there's no gadget container yet, no proxy implementation etc;
> If
> > > you
> > > >  > > just want a fully functional php shindig server, please wait a
> > > little
> > > >  > > more since this is nothing but a code preview :)
> > > >  > >
> > > >  > >        -- Chris
> > > >  > >
> > > >  > >
> > > >  >
> > > >
> > >
> >
> >
>

Re: php shindig - progress report

[Akash Xavier <ak...@gmail.com>]

Chris,
I was developing a parallel container in php after I noticed that Shndig php
is primitive. But happy that someone is working. My container code is very
kiddish.
If there's anything I can work on, please do tell me.

On Sat, Feb 23, 2008 at 8:46 PM, Akash Xavier <ak...@gmail.com>
wrote:

> Chris,
>
> I don't remember where, but sometime ago I read that
> http://shindig
> .chabotc.com/ifr/?url=(http://www.labpixies.com/campaigns/todo/todo.xml)<http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/todo.xml>
> would be better than
> http://shindig
> .chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/todo.xml
>
>
> On Fri, Feb 22, 2008 at 3:22 AM, Chris Chabot <ch...@xs4all.nl> wrote:
>
> > Thanks, was wondering why you linked a .js :)
> >
> > Once i have the proxy, js and rpc servlet ports done (working on those
> > now), some popper testing was next on the list so this will be a
> > useful tool.
> >
> > ps on my demo server i've made a opensocial-0.7 feature directory
> > which contains the opensocial-reference content, so it can run it
> > without having to edit the compliancetests.xml file.
> >
> > Oh and btw, what would be the easiest way to test all of this in a
> > container environment, presumable just take the samplecontainer and go
> > from there? Any gotcha's i should be aware off?
> >
> >        -- Chris
> >
> > On Feb 22, 2008, at 7:09 AM, Cassie wrote:
> >
> > > ha, and by that link (which ends mistakenly in .js) i really meant:
> > >
> > http://opensocial-resources.googlecode.com/svn/tests/trunk/compliancetests.xml
> > >
> > > On Thu, Feb 21, 2008 at 9:53 PM, Cassie <do...@apache.org> wrote:
> > >
> > >> btw - the initial compliance tests are here:
> > >>
> > >>
> > http://opensocial-resources.googlecode.com/svn/tests/trunk/compliancetests.js
> > >>
> > >> (these are a wip, any patches are very welcome!)
> > >>
> > >> - Cassie
> > >>
> > >>
> > >>
> > >> On Thu, Feb 21, 2008 at 7:32 PM, Kevin Marks <ke...@gmail.com>
> > >> wrote:
> > >>
> > >>> Trying out Cassie's initial spec compliance app which I had to
> > >>> modify
> > >>> to:
> > >>> <Require feature="opensocial-samplecontainer"/>
> > >>> instead of
> > >>> <Require feature="opensocial-0.7"/>
> > >>>
> > >>> you can see that you're getting there. Presumably not having any
> > >>> owner info is due to a lack of a real db backend?
> > >>>
> > >>> Great progress, looking forward to seeing this soon; we have a lot
> > >>> of
> > >>> people interested in a fuller PHP version.
> > >>>
> > >>> On Thu, Feb 21, 2008 at 9:45 AM, Cassie <do...@apache.org> wrote:
> > >>>> So Shindig definitely needs its own tests. The spec will only
> > >>>> include
> > >>>> compliance tests because thats all it can/should enforce.
> > >>>> Compliance
> > >>> tests
> > >>>> will never be equivalent to a regular testing suite because the
> > >>>> spec
> > >>> allows
> > >>>> a lot of different ways to handle one call.
> > >>>>
> > >>>> It can't test for instance that a person's name field is equal to
> > >>> what you
> > >>>> think it should be. That could only be in a shindig specific test.
> > >>> The
> > >>>> compliance test would only make sure that the call returned an
> > >>>> opensocial.Name object and had at least one field filled out.
> > >>>>
> > >>>> Hope that helps explain things.
> > >>>>
> > >>>> - Cassie
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>> On Thu, Feb 21, 2008 at 9:15 AM, Bruno Bowden <br...@google.com>
> > >>> wrote:
> > >>>>
> > >>>>> Fantastic Chris. Thanks for the contributions.
> > >>>>>
> > >>>>> To help keep the two versions in sync, we should have test cases
> > >>> that can
> > >>>>> be
> > >>>>> run against both versions. That's something that belongs with the
> > >>> spec and
> > >>>>> outside of Shindig.
> > >>>>>
> > >>>>>
> > >>>>> On Thu, Feb 21, 2008 at 4:30 AM, Chris Chabot <ch...@xs4all.nl>
> > >>> wrote:
> > >>>>>
> > >>>>>> Hey guys,
> > >>>>>>
> > >>>>>> Since no one likes to hear "it's being worked on" without being
> > >>> able
> > >>>>>> to see it, and i now have the first visible workings of a php
> > >>> version
> > >>>>>> i thought i'd post a bit of a progress report.
> > >>>>>>
> > >>>>>> I've been working for the last 7 or 8 days on a php port of the
> > >>> java
> > >>>>>> shindig code, I've chosen to follow the structure as closely as
> > >>>>>> possible where the language differences allows for it to make
> > >>>>>> supporting the same features and having the same behavior easier.
> > >>> Now
> > >>>>>> it's been a bit of a challenge, partially because the last time
> > >>> I've
> > >>>>>> read any java code is 8 years behind me, and partially since it's
> > >>> a
> > >>>>>> huge undertaking to port an entire large feature set and service
> > >>>>>> without being able to test it until all the components are done,
> > >>> and
> > >>>>>> php being a completely different environment then the java/jetty
> > >>> one.
> > >>>>>>
> > >>>>>> I've now reached the point where the basic structure is working,
> > >>> and
> > >>>>>> it successfully renders the todo.xml gadget into a valid and
> > >>> correct
> > >>>>>> gadget.
> > >>>>>>
> > >>>>>> I'm still working on the js, rpc, proxy and gadget token bits so
> > >>> their
> > >>>>>> not included in this, also the remote content gadgets are not
> > >>>>>> supported yet (though that will be very quick to follow).
> > >>>>>>
> > >>>>>> I expect to have those lacking bits done in the near future, and
> > >>>>>> combined with a good bit of testing i hope to have a 'patch'
> > >>> ready for
> > >>>>>> submission soonish (and i need to formalize the permission to
> > >>> submit
> > >>>>>> it under the apache license with my employer, but that is a mere
> > >>>>>> formality).
> > >>>>>>
> > >>>>>> Feature wise it's completely compatible to the java cousin,
> > >>> including
> > >>>>>> the 'features', message bundle, etc support and only the
> > >>> GadgetServer,
> > >>>>>> web service and caching parts are different from the java version
> > >>> (in
> > >>>>>> memory caching for instance couldn't work in a multi process php
> > >>>>>> environment), and i think i'll soon add a few more php specific
> > >>>>>> optimizations soon to speed the whole thing up a bit as well.
> > >>>>>>
> > >>>>>> The code i'm using for porting is from feb 14th, i'll evaluate
> > >>> the
> > >>>>>> patches that happen in the meantime once i've got everything
> > >>> done,
> > >>>>>> since doing both would be to much of a strain progress right now.
> > >>>>>>
> > >>>>>> A working demo can be seen here:
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>>
> > http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/todo.xml
> > >>>>>>
> > >>>>>> And the code-so-far for those who are interested in a sneak
> > >>> preview of
> > >>>>>> it is here:
> > >>>>>> http://www.chabotc.com/php-shindig.tar.gz
> > >>>>>>
> > >>>>>> Please do keep in mind that it's still work in progress, so i
> > >>> know
> > >>>>>> there's no gadget container yet, no proxy implementation etc; If
> > >>> you
> > >>>>>> just want a fully functional php shindig server, please wait a
> > >>> little
> > >>>>>> more since this is nothing but a code preview :)
> > >>>>>>
> > >>>>>>       -- Chris
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>>>
> > >>>
> > >>
> > >>
> >
> >
>
>
> --
> Akash Xavier
> akashmanohar@gmail.com




-- 
Akash Xavier
akashmanohar@gmail.com

Re: php shindig - progress report

[Akash Xavier <ak...@gmail.com>]

Chris,

I don't remember where, but sometime ago I read that
http://shindig
.chabotc.com/ifr/?url=(http://www.labpixies.com/campaigns/todo/todo.xml)<http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/todo.xml>
would be better than
http://shindig
.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/todo.xml


On Fri, Feb 22, 2008 at 3:22 AM, Chris Chabot <ch...@xs4all.nl> wrote:

> Thanks, was wondering why you linked a .js :)
>
> Once i have the proxy, js and rpc servlet ports done (working on those
> now), some popper testing was next on the list so this will be a
> useful tool.
>
> ps on my demo server i've made a opensocial-0.7 feature directory
> which contains the opensocial-reference content, so it can run it
> without having to edit the compliancetests.xml file.
>
> Oh and btw, what would be the easiest way to test all of this in a
> container environment, presumable just take the samplecontainer and go
> from there? Any gotcha's i should be aware off?
>
>        -- Chris
>
> On Feb 22, 2008, at 7:09 AM, Cassie wrote:
>
> > ha, and by that link (which ends mistakenly in .js) i really meant:
> >
> http://opensocial-resources.googlecode.com/svn/tests/trunk/compliancetests.xml
> >
> > On Thu, Feb 21, 2008 at 9:53 PM, Cassie <do...@apache.org> wrote:
> >
> >> btw - the initial compliance tests are here:
> >>
> >>
> http://opensocial-resources.googlecode.com/svn/tests/trunk/compliancetests.js
> >>
> >> (these are a wip, any patches are very welcome!)
> >>
> >> - Cassie
> >>
> >>
> >>
> >> On Thu, Feb 21, 2008 at 7:32 PM, Kevin Marks <ke...@gmail.com>
> >> wrote:
> >>
> >>> Trying out Cassie's initial spec compliance app which I had to
> >>> modify
> >>> to:
> >>> <Require feature="opensocial-samplecontainer"/>
> >>> instead of
> >>> <Require feature="opensocial-0.7"/>
> >>>
> >>> you can see that you're getting there. Presumably not having any
> >>> owner info is due to a lack of a real db backend?
> >>>
> >>> Great progress, looking forward to seeing this soon; we have a lot
> >>> of
> >>> people interested in a fuller PHP version.
> >>>
> >>> On Thu, Feb 21, 2008 at 9:45 AM, Cassie <do...@apache.org> wrote:
> >>>> So Shindig definitely needs its own tests. The spec will only
> >>>> include
> >>>> compliance tests because thats all it can/should enforce.
> >>>> Compliance
> >>> tests
> >>>> will never be equivalent to a regular testing suite because the
> >>>> spec
> >>> allows
> >>>> a lot of different ways to handle one call.
> >>>>
> >>>> It can't test for instance that a person's name field is equal to
> >>> what you
> >>>> think it should be. That could only be in a shindig specific test.
> >>> The
> >>>> compliance test would only make sure that the call returned an
> >>>> opensocial.Name object and had at least one field filled out.
> >>>>
> >>>> Hope that helps explain things.
> >>>>
> >>>> - Cassie
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> On Thu, Feb 21, 2008 at 9:15 AM, Bruno Bowden <br...@google.com>
> >>> wrote:
> >>>>
> >>>>> Fantastic Chris. Thanks for the contributions.
> >>>>>
> >>>>> To help keep the two versions in sync, we should have test cases
> >>> that can
> >>>>> be
> >>>>> run against both versions. That's something that belongs with the
> >>> spec and
> >>>>> outside of Shindig.
> >>>>>
> >>>>>
> >>>>> On Thu, Feb 21, 2008 at 4:30 AM, Chris Chabot <ch...@xs4all.nl>
> >>> wrote:
> >>>>>
> >>>>>> Hey guys,
> >>>>>>
> >>>>>> Since no one likes to hear "it's being worked on" without being
> >>> able
> >>>>>> to see it, and i now have the first visible workings of a php
> >>> version
> >>>>>> i thought i'd post a bit of a progress report.
> >>>>>>
> >>>>>> I've been working for the last 7 or 8 days on a php port of the
> >>> java
> >>>>>> shindig code, I've chosen to follow the structure as closely as
> >>>>>> possible where the language differences allows for it to make
> >>>>>> supporting the same features and having the same behavior easier.
> >>> Now
> >>>>>> it's been a bit of a challenge, partially because the last time
> >>> I've
> >>>>>> read any java code is 8 years behind me, and partially since it's
> >>> a
> >>>>>> huge undertaking to port an entire large feature set and service
> >>>>>> without being able to test it until all the components are done,
> >>> and
> >>>>>> php being a completely different environment then the java/jetty
> >>> one.
> >>>>>>
> >>>>>> I've now reached the point where the basic structure is working,
> >>> and
> >>>>>> it successfully renders the todo.xml gadget into a valid and
> >>> correct
> >>>>>> gadget.
> >>>>>>
> >>>>>> I'm still working on the js, rpc, proxy and gadget token bits so
> >>> their
> >>>>>> not included in this, also the remote content gadgets are not
> >>>>>> supported yet (though that will be very quick to follow).
> >>>>>>
> >>>>>> I expect to have those lacking bits done in the near future, and
> >>>>>> combined with a good bit of testing i hope to have a 'patch'
> >>> ready for
> >>>>>> submission soonish (and i need to formalize the permission to
> >>> submit
> >>>>>> it under the apache license with my employer, but that is a mere
> >>>>>> formality).
> >>>>>>
> >>>>>> Feature wise it's completely compatible to the java cousin,
> >>> including
> >>>>>> the 'features', message bundle, etc support and only the
> >>> GadgetServer,
> >>>>>> web service and caching parts are different from the java version
> >>> (in
> >>>>>> memory caching for instance couldn't work in a multi process php
> >>>>>> environment), and i think i'll soon add a few more php specific
> >>>>>> optimizations soon to speed the whole thing up a bit as well.
> >>>>>>
> >>>>>> The code i'm using for porting is from feb 14th, i'll evaluate
> >>> the
> >>>>>> patches that happen in the meantime once i've got everything
> >>> done,
> >>>>>> since doing both would be to much of a strain progress right now.
> >>>>>>
> >>>>>> A working demo can be seen here:
> >>>>>>
> >>>>>>
> >>>>>
> >>>
> http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/todo.xml
> >>>>>>
> >>>>>> And the code-so-far for those who are interested in a sneak
> >>> preview of
> >>>>>> it is here:
> >>>>>> http://www.chabotc.com/php-shindig.tar.gz
> >>>>>>
> >>>>>> Please do keep in mind that it's still work in progress, so i
> >>> know
> >>>>>> there's no gadget container yet, no proxy implementation etc; If
> >>> you
> >>>>>> just want a fully functional php shindig server, please wait a
> >>> little
> >>>>>> more since this is nothing but a code preview :)
> >>>>>>
> >>>>>>       -- Chris
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >>
>
>


-- 
Akash Xavier
akashmanohar@gmail.com

Re: php shindig - progress report

[Chris Chabot <ch...@xs4all.nl>]

Thanks, was wondering why you linked a .js :)

Once i have the proxy, js and rpc servlet ports done (working on those  
now), some popper testing was next on the list so this will be a  
useful tool.

ps on my demo server i've made a opensocial-0.7 feature directory  
which contains the opensocial-reference content, so it can run it  
without having to edit the compliancetests.xml file.

Oh and btw, what would be the easiest way to test all of this in a  
container environment, presumable just take the samplecontainer and go  
from there? Any gotcha's i should be aware off?

	-- Chris

On Feb 22, 2008, at 7:09 AM, Cassie wrote:

> ha, and by that link (which ends mistakenly in .js) i really meant:
> http://opensocial-resources.googlecode.com/svn/tests/trunk/compliancetests.xml
>
> On Thu, Feb 21, 2008 at 9:53 PM, Cassie <do...@apache.org> wrote:
>
>> btw - the initial compliance tests are here:
>>
>> http://opensocial-resources.googlecode.com/svn/tests/trunk/compliancetests.js
>>
>> (these are a wip, any patches are very welcome!)
>>
>> - Cassie
>>
>>
>>
>> On Thu, Feb 21, 2008 at 7:32 PM, Kevin Marks <ke...@gmail.com>  
>> wrote:
>>
>>> Trying out Cassie's initial spec compliance app which I had to  
>>> modify
>>> to:
>>> <Require feature="opensocial-samplecontainer"/>
>>> instead of
>>> <Require feature="opensocial-0.7"/>
>>>
>>> you can see that you're getting there. Presumably not having any
>>> owner info is due to a lack of a real db backend?
>>>
>>> Great progress, looking forward to seeing this soon; we have a lot  
>>> of
>>> people interested in a fuller PHP version.
>>>
>>> On Thu, Feb 21, 2008 at 9:45 AM, Cassie <do...@apache.org> wrote:
>>>> So Shindig definitely needs its own tests. The spec will only  
>>>> include
>>>> compliance tests because thats all it can/should enforce.  
>>>> Compliance
>>> tests
>>>> will never be equivalent to a regular testing suite because the  
>>>> spec
>>> allows
>>>> a lot of different ways to handle one call.
>>>>
>>>> It can't test for instance that a person's name field is equal to
>>> what you
>>>> think it should be. That could only be in a shindig specific test.
>>> The
>>>> compliance test would only make sure that the call returned an
>>>> opensocial.Name object and had at least one field filled out.
>>>>
>>>> Hope that helps explain things.
>>>>
>>>> - Cassie
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, Feb 21, 2008 at 9:15 AM, Bruno Bowden <br...@google.com>
>>> wrote:
>>>>
>>>>> Fantastic Chris. Thanks for the contributions.
>>>>>
>>>>> To help keep the two versions in sync, we should have test cases
>>> that can
>>>>> be
>>>>> run against both versions. That's something that belongs with the
>>> spec and
>>>>> outside of Shindig.
>>>>>
>>>>>
>>>>> On Thu, Feb 21, 2008 at 4:30 AM, Chris Chabot <ch...@xs4all.nl>
>>> wrote:
>>>>>
>>>>>> Hey guys,
>>>>>>
>>>>>> Since no one likes to hear "it's being worked on" without being
>>> able
>>>>>> to see it, and i now have the first visible workings of a php
>>> version
>>>>>> i thought i'd post a bit of a progress report.
>>>>>>
>>>>>> I've been working for the last 7 or 8 days on a php port of the
>>> java
>>>>>> shindig code, I've chosen to follow the structure as closely as
>>>>>> possible where the language differences allows for it to make
>>>>>> supporting the same features and having the same behavior easier.
>>> Now
>>>>>> it's been a bit of a challenge, partially because the last time
>>> I've
>>>>>> read any java code is 8 years behind me, and partially since it's
>>> a
>>>>>> huge undertaking to port an entire large feature set and service
>>>>>> without being able to test it until all the components are done,
>>> and
>>>>>> php being a completely different environment then the java/jetty
>>> one.
>>>>>>
>>>>>> I've now reached the point where the basic structure is working,
>>> and
>>>>>> it successfully renders the todo.xml gadget into a valid and
>>> correct
>>>>>> gadget.
>>>>>>
>>>>>> I'm still working on the js, rpc, proxy and gadget token bits so
>>> their
>>>>>> not included in this, also the remote content gadgets are not
>>>>>> supported yet (though that will be very quick to follow).
>>>>>>
>>>>>> I expect to have those lacking bits done in the near future, and
>>>>>> combined with a good bit of testing i hope to have a 'patch'
>>> ready for
>>>>>> submission soonish (and i need to formalize the permission to
>>> submit
>>>>>> it under the apache license with my employer, but that is a mere
>>>>>> formality).
>>>>>>
>>>>>> Feature wise it's completely compatible to the java cousin,
>>> including
>>>>>> the 'features', message bundle, etc support and only the
>>> GadgetServer,
>>>>>> web service and caching parts are different from the java version
>>> (in
>>>>>> memory caching for instance couldn't work in a multi process php
>>>>>> environment), and i think i'll soon add a few more php specific
>>>>>> optimizations soon to speed the whole thing up a bit as well.
>>>>>>
>>>>>> The code i'm using for porting is from feb 14th, i'll evaluate
>>> the
>>>>>> patches that happen in the meantime once i've got everything
>>> done,
>>>>>> since doing both would be to much of a strain progress right now.
>>>>>>
>>>>>> A working demo can be seen here:
>>>>>>
>>>>>>
>>>>>
>>> http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/todo.xml
>>>>>>
>>>>>> And the code-so-far for those who are interested in a sneak
>>> preview of
>>>>>> it is here:
>>>>>> http://www.chabotc.com/php-shindig.tar.gz
>>>>>>
>>>>>> Please do keep in mind that it's still work in progress, so i
>>> know
>>>>>> there's no gadget container yet, no proxy implementation etc; If
>>> you
>>>>>> just want a fully functional php shindig server, please wait a
>>> little
>>>>>> more since this is nothing but a code preview :)
>>>>>>
>>>>>>       -- Chris
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>>

Re: php shindig - progress report

[Cassie <do...@apache.org>]

ha, and by that link (which ends mistakenly in .js) i really meant:
http://opensocial-resources.googlecode.com/svn/tests/trunk/compliancetests.xml

On Thu, Feb 21, 2008 at 9:53 PM, Cassie <do...@apache.org> wrote:

> btw - the initial compliance tests are here:
>
> http://opensocial-resources.googlecode.com/svn/tests/trunk/compliancetests.js
>
> (these are a wip, any patches are very welcome!)
>
> - Cassie
>
>
>
> On Thu, Feb 21, 2008 at 7:32 PM, Kevin Marks <ke...@gmail.com> wrote:
>
> > Trying out Cassie's initial spec compliance app which I had to modify
> > to:
> > <Require feature="opensocial-samplecontainer"/>
> > instead of
> > <Require feature="opensocial-0.7"/>
> >
> >  you can see that you're getting there. Presumably not having any
> > owner info is due to a lack of a real db backend?
> >
> > Great progress, looking forward to seeing this soon; we have a lot of
> > people interested in a fuller PHP version.
> >
> > On Thu, Feb 21, 2008 at 9:45 AM, Cassie <do...@apache.org> wrote:
> > > So Shindig definitely needs its own tests. The spec will only include
> > >  compliance tests because thats all it can/should enforce. Compliance
> > tests
> > >  will never be equivalent to a regular testing suite because the spec
> > allows
> > >  a lot of different ways to handle one call.
> > >
> > >  It can't test for instance that a person's name field is equal to
> > what you
> > >  think it should be. That could only be in a shindig specific test.
> > The
> > >  compliance test would only make sure that the call returned an
> > >  opensocial.Name object and had at least one field filled out.
> > >
> > >  Hope that helps explain things.
> > >
> > >  - Cassie
> > >
> > >
> > >
> > >
> > >  On Thu, Feb 21, 2008 at 9:15 AM, Bruno Bowden <br...@google.com>
> > wrote:
> > >
> > >  > Fantastic Chris. Thanks for the contributions.
> > >  >
> > >  > To help keep the two versions in sync, we should have test cases
> > that can
> > >  > be
> > >  > run against both versions. That's something that belongs with the
> > spec and
> > >  > outside of Shindig.
> > >  >
> > >  >
> > >  > On Thu, Feb 21, 2008 at 4:30 AM, Chris Chabot <ch...@xs4all.nl>
> > wrote:
> > >  >
> > >  > > Hey guys,
> > >  > >
> > >  > > Since no one likes to hear "it's being worked on" without being
> > able
> > >  > > to see it, and i now have the first visible workings of a php
> > version
> > >  > > i thought i'd post a bit of a progress report.
> > >  > >
> > >  > > I've been working for the last 7 or 8 days on a php port of the
> > java
> > >  > > shindig code, I've chosen to follow the structure as closely as
> > >  > > possible where the language differences allows for it to make
> > >  > > supporting the same features and having the same behavior easier.
> > Now
> > >  > > it's been a bit of a challenge, partially because the last time
> > I've
> > >  > > read any java code is 8 years behind me, and partially since it's
> > a
> > >  > > huge undertaking to port an entire large feature set and service
> > >  > > without being able to test it until all the components are done,
> > and
> > >  > > php being a completely different environment then the java/jetty
> > one.
> > >  > >
> > >  > > I've now reached the point where the basic structure is working,
> > and
> > >  > > it successfully renders the todo.xml gadget into a valid and
> > correct
> > >  > > gadget.
> > >  > >
> > >  > > I'm still working on the js, rpc, proxy and gadget token bits so
> > their
> > >  > > not included in this, also the remote content gadgets are not
> > >  > > supported yet (though that will be very quick to follow).
> > >  > >
> > >  > > I expect to have those lacking bits done in the near future, and
> > >  > > combined with a good bit of testing i hope to have a 'patch'
> > ready for
> > >  > > submission soonish (and i need to formalize the permission to
> > submit
> > >  > > it under the apache license with my employer, but that is a mere
> > >  > > formality).
> > >  > >
> > >  > > Feature wise it's completely compatible to the java cousin,
> > including
> > >  > > the 'features', message bundle, etc support and only the
> > GadgetServer,
> > >  > > web service and caching parts are different from the java version
> > (in
> > >  > > memory caching for instance couldn't work in a multi process php
> > >  > > environment), and i think i'll soon add a few more php specific
> > >  > > optimizations soon to speed the whole thing up a bit as well.
> > >  > >
> > >  > > The code i'm using for porting is from feb 14th, i'll evaluate
> > the
> > >  > > patches that happen in the meantime once i've got everything
> > done,
> > >  > > since doing both would be to much of a strain progress right now.
> > >  > >
> > >  > > A working demo can be seen here:
> > >  > >
> > >  > >
> > >  >
> > http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/todo.xml
> > >  > >
> > >  > > And the code-so-far for those who are interested in a sneak
> > preview of
> > >  > > it is here:
> > >  > > http://www.chabotc.com/php-shindig.tar.gz
> > >  > >
> > >  > > Please do keep in mind that it's still work in progress, so i
> > know
> > >  > > there's no gadget container yet, no proxy implementation etc; If
> > you
> > >  > > just want a fully functional php shindig server, please wait a
> > little
> > >  > > more since this is nothing but a code preview :)
> > >  > >
> > >  > >        -- Chris
> > >  > >
> > >  > >
> > >  >
> > >
> >
>
>

Re: php shindig - progress report

[Cassie <do...@apache.org>]

btw - the initial compliance tests are here:
http://opensocial-resources.googlecode.com/svn/tests/trunk/compliancetests.js

(these are a wip, any patches are very welcome!)

- Cassie


On Thu, Feb 21, 2008 at 7:32 PM, Kevin Marks <ke...@gmail.com> wrote:

> Trying out Cassie's initial spec compliance app which I had to modify to:
> <Require feature="opensocial-samplecontainer"/>
> instead of
> <Require feature="opensocial-0.7"/>
>
>  you can see that you're getting there. Presumably not having any
> owner info is due to a lack of a real db backend?
>
> Great progress, looking forward to seeing this soon; we have a lot of
> people interested in a fuller PHP version.
>
> On Thu, Feb 21, 2008 at 9:45 AM, Cassie <do...@apache.org> wrote:
> > So Shindig definitely needs its own tests. The spec will only include
> >  compliance tests because thats all it can/should enforce. Compliance
> tests
> >  will never be equivalent to a regular testing suite because the spec
> allows
> >  a lot of different ways to handle one call.
> >
> >  It can't test for instance that a person's name field is equal to what
> you
> >  think it should be. That could only be in a shindig specific test. The
> >  compliance test would only make sure that the call returned an
> >  opensocial.Name object and had at least one field filled out.
> >
> >  Hope that helps explain things.
> >
> >  - Cassie
> >
> >
> >
> >
> >  On Thu, Feb 21, 2008 at 9:15 AM, Bruno Bowden <br...@google.com> wrote:
> >
> >  > Fantastic Chris. Thanks for the contributions.
> >  >
> >  > To help keep the two versions in sync, we should have test cases that
> can
> >  > be
> >  > run against both versions. That's something that belongs with the
> spec and
> >  > outside of Shindig.
> >  >
> >  >
> >  > On Thu, Feb 21, 2008 at 4:30 AM, Chris Chabot <ch...@xs4all.nl>
> wrote:
> >  >
> >  > > Hey guys,
> >  > >
> >  > > Since no one likes to hear "it's being worked on" without being
> able
> >  > > to see it, and i now have the first visible workings of a php
> version
> >  > > i thought i'd post a bit of a progress report.
> >  > >
> >  > > I've been working for the last 7 or 8 days on a php port of the
> java
> >  > > shindig code, I've chosen to follow the structure as closely as
> >  > > possible where the language differences allows for it to make
> >  > > supporting the same features and having the same behavior easier.
> Now
> >  > > it's been a bit of a challenge, partially because the last time
> I've
> >  > > read any java code is 8 years behind me, and partially since it's a
> >  > > huge undertaking to port an entire large feature set and service
> >  > > without being able to test it until all the components are done,
> and
> >  > > php being a completely different environment then the java/jetty
> one.
> >  > >
> >  > > I've now reached the point where the basic structure is working,
> and
> >  > > it successfully renders the todo.xml gadget into a valid and
> correct
> >  > > gadget.
> >  > >
> >  > > I'm still working on the js, rpc, proxy and gadget token bits so
> their
> >  > > not included in this, also the remote content gadgets are not
> >  > > supported yet (though that will be very quick to follow).
> >  > >
> >  > > I expect to have those lacking bits done in the near future, and
> >  > > combined with a good bit of testing i hope to have a 'patch' ready
> for
> >  > > submission soonish (and i need to formalize the permission to
> submit
> >  > > it under the apache license with my employer, but that is a mere
> >  > > formality).
> >  > >
> >  > > Feature wise it's completely compatible to the java cousin,
> including
> >  > > the 'features', message bundle, etc support and only the
> GadgetServer,
> >  > > web service and caching parts are different from the java version
> (in
> >  > > memory caching for instance couldn't work in a multi process php
> >  > > environment), and i think i'll soon add a few more php specific
> >  > > optimizations soon to speed the whole thing up a bit as well.
> >  > >
> >  > > The code i'm using for porting is from feb 14th, i'll evaluate the
> >  > > patches that happen in the meantime once i've got everything done,
> >  > > since doing both would be to much of a strain progress right now.
> >  > >
> >  > > A working demo can be seen here:
> >  > >
> >  > >
> >  >
> http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/todo.xml
> >  > >
> >  > > And the code-so-far for those who are interested in a sneak preview
> of
> >  > > it is here:
> >  > > http://www.chabotc.com/php-shindig.tar.gz
> >  > >
> >  > > Please do keep in mind that it's still work in progress, so i know
> >  > > there's no gadget container yet, no proxy implementation etc; If
> you
> >  > > just want a fully functional php shindig server, please wait a
> little
> >  > > more since this is nothing but a code preview :)
> >  > >
> >  > >        -- Chris
> >  > >
> >  > >
> >  >
> >
>

Re: php shindig - progress report

[Kevin Marks <ke...@gmail.com>]

Trying out Cassie's initial spec compliance app which I had to modify to:
<Require feature="opensocial-samplecontainer"/>
instead of
<Require feature="opensocial-0.7"/>

 you can see that you're getting there. Presumably not having any
owner info is due to a lack of a real db backend?

Great progress, looking forward to seeing this soon; we have a lot of
people interested in a fuller PHP version.

On Thu, Feb 21, 2008 at 9:45 AM, Cassie <do...@apache.org> wrote:
> So Shindig definitely needs its own tests. The spec will only include
>  compliance tests because thats all it can/should enforce. Compliance tests
>  will never be equivalent to a regular testing suite because the spec allows
>  a lot of different ways to handle one call.
>
>  It can't test for instance that a person's name field is equal to what you
>  think it should be. That could only be in a shindig specific test. The
>  compliance test would only make sure that the call returned an
>  opensocial.Name object and had at least one field filled out.
>
>  Hope that helps explain things.
>
>  - Cassie
>
>
>
>
>  On Thu, Feb 21, 2008 at 9:15 AM, Bruno Bowden <br...@google.com> wrote:
>
>  > Fantastic Chris. Thanks for the contributions.
>  >
>  > To help keep the two versions in sync, we should have test cases that can
>  > be
>  > run against both versions. That's something that belongs with the spec and
>  > outside of Shindig.
>  >
>  >
>  > On Thu, Feb 21, 2008 at 4:30 AM, Chris Chabot <ch...@xs4all.nl> wrote:
>  >
>  > > Hey guys,
>  > >
>  > > Since no one likes to hear "it's being worked on" without being able
>  > > to see it, and i now have the first visible workings of a php version
>  > > i thought i'd post a bit of a progress report.
>  > >
>  > > I've been working for the last 7 or 8 days on a php port of the java
>  > > shindig code, I've chosen to follow the structure as closely as
>  > > possible where the language differences allows for it to make
>  > > supporting the same features and having the same behavior easier. Now
>  > > it's been a bit of a challenge, partially because the last time I've
>  > > read any java code is 8 years behind me, and partially since it's a
>  > > huge undertaking to port an entire large feature set and service
>  > > without being able to test it until all the components are done, and
>  > > php being a completely different environment then the java/jetty one.
>  > >
>  > > I've now reached the point where the basic structure is working, and
>  > > it successfully renders the todo.xml gadget into a valid and correct
>  > > gadget.
>  > >
>  > > I'm still working on the js, rpc, proxy and gadget token bits so their
>  > > not included in this, also the remote content gadgets are not
>  > > supported yet (though that will be very quick to follow).
>  > >
>  > > I expect to have those lacking bits done in the near future, and
>  > > combined with a good bit of testing i hope to have a 'patch' ready for
>  > > submission soonish (and i need to formalize the permission to submit
>  > > it under the apache license with my employer, but that is a mere
>  > > formality).
>  > >
>  > > Feature wise it's completely compatible to the java cousin, including
>  > > the 'features', message bundle, etc support and only the GadgetServer,
>  > > web service and caching parts are different from the java version (in
>  > > memory caching for instance couldn't work in a multi process php
>  > > environment), and i think i'll soon add a few more php specific
>  > > optimizations soon to speed the whole thing up a bit as well.
>  > >
>  > > The code i'm using for porting is from feb 14th, i'll evaluate the
>  > > patches that happen in the meantime once i've got everything done,
>  > > since doing both would be to much of a strain progress right now.
>  > >
>  > > A working demo can be seen here:
>  > >
>  > >
>  > http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/todo.xml
>  > >
>  > > And the code-so-far for those who are interested in a sneak preview of
>  > > it is here:
>  > > http://www.chabotc.com/php-shindig.tar.gz
>  > >
>  > > Please do keep in mind that it's still work in progress, so i know
>  > > there's no gadget container yet, no proxy implementation etc; If you
>  > > just want a fully functional php shindig server, please wait a little
>  > > more since this is nothing but a code preview :)
>  > >
>  > >        -- Chris
>  > >
>  > >
>  >
>

Re: php shindig - progress report

[Cassie <do...@apache.org>]

So Shindig definitely needs its own tests. The spec will only include
compliance tests because thats all it can/should enforce. Compliance tests
will never be equivalent to a regular testing suite because the spec allows
a lot of different ways to handle one call.

It can't test for instance that a person's name field is equal to what you
think it should be. That could only be in a shindig specific test. The
compliance test would only make sure that the call returned an
opensocial.Name object and had at least one field filled out.

Hope that helps explain things.

- Cassie


On Thu, Feb 21, 2008 at 9:15 AM, Bruno Bowden <br...@google.com> wrote:

> Fantastic Chris. Thanks for the contributions.
>
> To help keep the two versions in sync, we should have test cases that can
> be
> run against both versions. That's something that belongs with the spec and
> outside of Shindig.
>
>
> On Thu, Feb 21, 2008 at 4:30 AM, Chris Chabot <ch...@xs4all.nl> wrote:
>
> > Hey guys,
> >
> > Since no one likes to hear "it's being worked on" without being able
> > to see it, and i now have the first visible workings of a php version
> > i thought i'd post a bit of a progress report.
> >
> > I've been working for the last 7 or 8 days on a php port of the java
> > shindig code, I've chosen to follow the structure as closely as
> > possible where the language differences allows for it to make
> > supporting the same features and having the same behavior easier. Now
> > it's been a bit of a challenge, partially because the last time I've
> > read any java code is 8 years behind me, and partially since it's a
> > huge undertaking to port an entire large feature set and service
> > without being able to test it until all the components are done, and
> > php being a completely different environment then the java/jetty one.
> >
> > I've now reached the point where the basic structure is working, and
> > it successfully renders the todo.xml gadget into a valid and correct
> > gadget.
> >
> > I'm still working on the js, rpc, proxy and gadget token bits so their
> > not included in this, also the remote content gadgets are not
> > supported yet (though that will be very quick to follow).
> >
> > I expect to have those lacking bits done in the near future, and
> > combined with a good bit of testing i hope to have a 'patch' ready for
> > submission soonish (and i need to formalize the permission to submit
> > it under the apache license with my employer, but that is a mere
> > formality).
> >
> > Feature wise it's completely compatible to the java cousin, including
> > the 'features', message bundle, etc support and only the GadgetServer,
> > web service and caching parts are different from the java version (in
> > memory caching for instance couldn't work in a multi process php
> > environment), and i think i'll soon add a few more php specific
> > optimizations soon to speed the whole thing up a bit as well.
> >
> > The code i'm using for porting is from feb 14th, i'll evaluate the
> > patches that happen in the meantime once i've got everything done,
> > since doing both would be to much of a strain progress right now.
> >
> > A working demo can be seen here:
> >
> >
> http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/todo.xml
> >
> > And the code-so-far for those who are interested in a sneak preview of
> > it is here:
> > http://www.chabotc.com/php-shindig.tar.gz
> >
> > Please do keep in mind that it's still work in progress, so i know
> > there's no gadget container yet, no proxy implementation etc; If you
> > just want a fully functional php shindig server, please wait a little
> > more since this is nothing but a code preview :)
> >
> >        -- Chris
> >
> >
>

Re: php shindig - progress report

[Bruno Bowden <br...@google.com>]

Fantastic Chris. Thanks for the contributions.

To help keep the two versions in sync, we should have test cases that can be
run against both versions. That's something that belongs with the spec and
outside of Shindig.


On Thu, Feb 21, 2008 at 4:30 AM, Chris Chabot <ch...@xs4all.nl> wrote:

> Hey guys,
>
> Since no one likes to hear "it's being worked on" without being able
> to see it, and i now have the first visible workings of a php version
> i thought i'd post a bit of a progress report.
>
> I've been working for the last 7 or 8 days on a php port of the java
> shindig code, I've chosen to follow the structure as closely as
> possible where the language differences allows for it to make
> supporting the same features and having the same behavior easier. Now
> it's been a bit of a challenge, partially because the last time I've
> read any java code is 8 years behind me, and partially since it's a
> huge undertaking to port an entire large feature set and service
> without being able to test it until all the components are done, and
> php being a completely different environment then the java/jetty one.
>
> I've now reached the point where the basic structure is working, and
> it successfully renders the todo.xml gadget into a valid and correct
> gadget.
>
> I'm still working on the js, rpc, proxy and gadget token bits so their
> not included in this, also the remote content gadgets are not
> supported yet (though that will be very quick to follow).
>
> I expect to have those lacking bits done in the near future, and
> combined with a good bit of testing i hope to have a 'patch' ready for
> submission soonish (and i need to formalize the permission to submit
> it under the apache license with my employer, but that is a mere
> formality).
>
> Feature wise it's completely compatible to the java cousin, including
> the 'features', message bundle, etc support and only the GadgetServer,
> web service and caching parts are different from the java version (in
> memory caching for instance couldn't work in a multi process php
> environment), and i think i'll soon add a few more php specific
> optimizations soon to speed the whole thing up a bit as well.
>
> The code i'm using for porting is from feb 14th, i'll evaluate the
> patches that happen in the meantime once i've got everything done,
> since doing both would be to much of a strain progress right now.
>
> A working demo can be seen here:
>
> http://shindig.chabotc.com/ifr/?url=http://www.labpixies.com/campaigns/todo/todo.xml
>
> And the code-so-far for those who are interested in a sneak preview of
> it is here:
> http://www.chabotc.com/php-shindig.tar.gz
>
> Please do keep in mind that it's still work in progress, so i know
> there's no gadget container yet, no proxy implementation etc; If you
> just want a fully functional php shindig server, please wait a little
> more since this is nothing but a code preview :)
>
>        -- Chris
>
>