Chris,
Is it running on your site chabotc.com? (you posted a link sometime ago)

On Sun, Mar 2, 2008 at 8:06 AM, Chris Chabot <[EMAIL PROTECTED]> wrote:

> Hey Guys,
>
> As you can see the patch for the new php shindig gadget server has
> landed. I've tested this server with all the simple gadgets i could
> get my hands on, and with sample containers, and it seems to behave
> identical to the java shindig server now (the one from feb 14th that
> is, what i based my porting efforts on).
>
> It's still missing a few things, including a good bit of extra
> documentation for all the classes etc, once this patch has been
> accepted i'll file bug reports for all the todo's that i have open,
> and desirable fixes/changes/etc, so that other people could easily get
> started on collaborating and expanding on this.
>
> When the patch has gone thru some basic review and is included in the
> svn repo, i would like to also apply for commit access to it. What
> would be the procedure for this?
>
> Look forward to your feedback!
>
>        -- Chris
>
> On Mar 2, 2008, at 4:56 PM, Chris Chabot (JIRA) wrote:
>
> > New PHP Shindig gadget server code
> > ----------------------------------
> >
> >                 Key: SHINDIG-103
> >                 URL: https://issues.apache.org/jira/browse/SHINDIG-103
> >             Project: Shindig
> >          Issue Type: Improvement
> >          Components: Gadgets Server - PHP
> >            Reporter: Chris Chabot
> >            Assignee: Brian McCallister
> >
> >
> > This patch completely replaces the old code in the php directory of
> > the shindig project, and replaces it with a port of the java shindig
> > code.
> >
> > The java code used is from a checkout from February the 14th, this
> > because keeping track of the changes while porting and testing would
> > have gotten in the way of completing the first release in a timely
> > fashion.
> >
> > It implements the structure and workings from the java server and
> > includes:
> > - Gadget server
> > - Proxy service
> > - JS service
> >
> > The maIn differences from the Java branch are:
> > - Different caching engine (abstracted base class, sample file
> > implementation included)
> > - Different gadget rendering work flow (no multithreading in PHP)
> > - No enum's or name spaced classes in php, so their top level
> > classes now
> > - Locale class to emulate the Java's Locale class
> > - Somewhat servlet like event handling to stay close to the Java's
> > structure
> >
> >
> > Missing is the RPC feature, some custom speedups to get it closer to
> > the Java's speed (it's about 40% slower right now, but that gap
> > might be fixed later on), and a better logging / error reporting
> > structure, it now only has a basic DEBUG flag in the config, which
> > if set, causes it to dump debug backtrace's on errors.
> >
> > It's also missing Caja support, since that is Java only at the
> > moment. Maybe somewhere in the future we'll have a command line
> > version available that we can use.
> >
> > It also contains a copy of the features directory structure (so that
> > it doesn't break on updates from the Java side of things, changes
> > will have to be implemented before you can copy over the new
> > version) and a copy of the sample container (minus the Caja
> > options), so that people can test it directly.
> >
> >
> >
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > You can reply to this email to add a comment to the issue online.
>
>


-- 
Akash Xavier
[EMAIL PROTECTED]

Reply via email to