Is the interest here to build a full server stack in Perl? One alternative I'd strongly consider is to use the Java server implementation as a black box, utilizing its RPC and rendering to provide the bulk of functionality while still providing a Perl API. This could ensure that functionality is always kept up-to-date, with all features supported, etc.
--John On Wed, Apr 2, 2008 at 3:14 PM, Paul Lindner <[EMAIL PROTECTED]> wrote: > Any Six Apart people on the list? If anyone is working on a perl > implementation it would be them. > > On 4/2/08 1:10 PM, "John Napiorkowski" <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > I'm new to the list but very excited about all the > > possibilities here. I know that people are working on > > multiple language implementations for Shindig but I > > don't see anyone working on a Perl version. I'm very > > interested in getting this started and looking to hook > > up with anyone of similar interest. Right now I am > > still reviewing all your existing documention, so I > > won't ask any more questions. > > > > If you are a Perl developer and want to join with me, > > please shout out. Right now my intention is to use > > the following Perl technologies: > > > > For Development: > > Moose > > (http://search.cpan.org/~stevan/Moose-0.40/lib/Moose.pm<http://search.cpan.org/%7Estevan/Moose-0.40/lib/Moose.pm> > ) > > > > and a modern Perl version, ( v5.8.8 or better) > > > > For handling HTTP: > > Catalyst (http://catalyst.perl.org/) > > > > Otherwise will decide on other core technologies when > > I finish reading all your docs! > > > > Thanks! > > > > > > > > > > > > > ______________________________________________________________________________ > > ______ > > You rock. That's why Blockbuster's offering you one month of Blockbuster > Total > > Access, No Cost. > > http://tc.deals.yahoo.com/tc/blockbuster/text5.com > >
