You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Paul Lindner <li...@inuus.com> on 2010/09/01 12:21:00 UTC
Last call for 2.0.0
I don't see any reason to not cut a 2.0.0 release now. Much of what's in
the pipeline is additive.
I'll start the build process today if no one objects.
--
Paul Lindner -- lindner@inuus.com -- linkedin.com/in/plindner
Re: Last call for 2.0.0
Posted by Janusz Dziemidowicz <ja...@nasza-klasa.pl>.
On Mon, Sep 6, 2010 at 2:10 PM, Gagandeep singh <ga...@gmail.com> wrote:
> Hi Janusz
>
> On Mon, Sep 6, 2010 at 2:55 PM, Janusz Dziemidowicz <
> janusz.dziemidowicz@nasza-klasa.pl> wrote:
>> - DefaultJsUriManager strictly validates if the request path is the
>> same as in configuration file. Since we are doing some rewriting along
>> the way I've had to replace the whole class. Should I file a bug in
>> Jira for that? (I don't believe this is a bug as such, but it would be
>> nice to be able to switch off this validation in shindig.properties,
>> other UriManagers already have such options).
>>
> What is the path you want for your js? Maybe you can override JS_PATH_PARAM
> = "gadgets.uri.js.path" for your container ?
That wouldn't solve my problem, since basically I need to have
different URLs for makeExternJsUri() and processExternJsUri().
Externally, JS code is visible under something like
http://opensocial.nk-net.pl/v09/gadgets/js/core (so it is what needs
to be set in gadgets.uri.js.path) but before it hits servers running
Shindig, it is processed by load balancer and rewritten to something
like http://SERVER_IP/APP_VERSION/gadgets/js/core Personally I do not
see much benefit of validating the URL in processExternJsUri(), so
I've had it disabled, which solves this problem for me.
--
Janusz Dziemidowicz
http://nk.pl
phone: +48500298526
email: janusz.dziemidowicz@nasza-klasa.pl
Nasza Klasa Sp. z o.o., ul. Gen. J. Bema 2
50-265 Wrocław
Sąd Rejonowy dla Wrocławia-Fabrycznej we Wrocławiu, VI Wydział
Gospodarczy Krajowego Rejestru Sądowego,
nr KRS:0000289629, NIP:898-21-22-104, REGON:020586020
Kapitał zakładowy: 67850 PLN
Re: Last call for 2.0.0
Posted by Gagandeep singh <ga...@gmail.com>.
Hi Janusz
On Mon, Sep 6, 2010 at 2:55 PM, Janusz Dziemidowicz <
janusz.dziemidowicz@nasza-klasa.pl> wrote:
> On Sat, Sep 4, 2010 at 1:41 AM, Paul Lindner <li...@inuus.com> wrote:
> > I'll be working on releasing 2.0.0 over the long weekend. There are a
> few
> > small issues that I'll deal with, but I don't see any major blockers.
>
> Hi,
> I'm responsible for OpenSocial in http://nk.pl Last week, I've
> migrated NK from shindig 1.1-BETA5 to 2.0.0-RC2. So there is already a
> production site running it:)
> Overall I'm quite happy (I was able to drop some hacks I've had to do
> on 1.1). I've encountered mainly two problems:
> - DefaultJsUriManager strictly validates if the request path is the
> same as in configuration file. Since we are doing some rewriting along
> the way I've had to replace the whole class. Should I file a bug in
> Jira for that? (I don't believe this is a bug as such, but it would be
> nice to be able to switch off this validation in shindig.properties,
> other UriManagers already have such options).
>
What is the path you want for your js? Maybe you can override JS_PATH_PARAM
= "gadgets.uri.js.path" for your container ?
- Proxy is broken with content rewriting (proxy returns original
> Content-Length header, but since rewritten content has different size
> it doesn't work). It is already fixed in trunk.
>
> --
> Janusz Dziemidowicz
> http://nk.pl
>
Re: Last call for 2.0.0
Posted by Janusz Dziemidowicz <ja...@nasza-klasa.pl>.
On Sat, Sep 4, 2010 at 1:41 AM, Paul Lindner <li...@inuus.com> wrote:
> I'll be working on releasing 2.0.0 over the long weekend. There are a few
> small issues that I'll deal with, but I don't see any major blockers.
Hi,
I'm responsible for OpenSocial in http://nk.pl Last week, I've
migrated NK from shindig 1.1-BETA5 to 2.0.0-RC2. So there is already a
production site running it:)
Overall I'm quite happy (I was able to drop some hacks I've had to do
on 1.1). I've encountered mainly two problems:
- DefaultJsUriManager strictly validates if the request path is the
same as in configuration file. Since we are doing some rewriting along
the way I've had to replace the whole class. Should I file a bug in
Jira for that? (I don't believe this is a bug as such, but it would be
nice to be able to switch off this validation in shindig.properties,
other UriManagers already have such options).
- Proxy is broken with content rewriting (proxy returns original
Content-Length header, but since rewritten content has different size
it doesn't work). It is already fixed in trunk.
--
Janusz Dziemidowicz
http://nk.pl
Re: Last call for 2.0.0
Posted by Paul Lindner <li...@inuus.com>.
I'll be working on releasing 2.0.0 over the long weekend. There are a few
small issues that I'll deal with, but I don't see any major blockers.
On Wed, Sep 1, 2010 at 3:21 AM, Paul Lindner <li...@inuus.com> wrote:
> I don't see any reason to not cut a 2.0.0 release now. Much of what's in
> the pipeline is additive.
>
> I'll start the build process today if no one objects.
>
>
> --
> Paul Lindner -- lindner@inuus.com -- linkedin.com/in/plindner
>
--
Paul Lindner -- lindner@inuus.com -- linkedin.com/in/plindner
Re: Last call for 2.0.0
Posted by Paul Lindner <pl...@linkedin.com>.
I'll respin 2.0.0 with this and a few other bug fixes.
On Tue, Sep 7, 2010 at 12:26 PM, Javier H Pedemonte <pe...@us.ibm.com>wrote:
> Any chance you could get this in:
> https://issues.apache.org/jira/browse/SHINDIG-1422? Small fix for
> shindig.uri.ext.
>
>
> Javier Pedemonte
>
--
Paul Lindner -- plindner@linkedin.com -- linkedin.com/in/plindner
Re: Last call for 2.0.0
Posted by Javier H Pedemonte <pe...@us.ibm.com>.
Any chance you could get this in:
https://issues.apache.org/jira/browse/SHINDIG-1422? Small fix for
shindig.uri.ext.
Javier Pedemonte
Re: Last call for 2.0.0
Posted by Mat Mannion <M....@warwick.ac.uk>.
We're planning a big-bang release of our portal (albeit, internally)
at the start of October. We're currently working off rc1 and all seems
to be in order for us - to work off a stable release would be good,
though :)
Mat
2010/9/1 Pablo Graña <pa...@globant.com>:
> is there anyone out there planning a near future release of a site based on
> 2.0.0?
>
> On Wed, Sep 1, 2010 at 7:21 AM, Paul Lindner <li...@inuus.com> wrote:
>
>> I don't see any reason to not cut a 2.0.0 release now. Much of what's in
>> the pipeline is additive.
>>
>> I'll start the build process today if no one objects.
>>
>>
>> --
>> Paul Lindner -- lindner@inuus.com -- linkedin.com/in/plindner
>>
>
>
>
> --
> Pablo Gra\~na
> Chief Architect
> Globant
> Arg Office: +54 (11) 4109 1743
> UK Office: +44 (20) 7043 8269 int 8043
> US Office: +1 (212) 400 7686 int 8043
>
--
Mat Mannion
Web Developer
IT Services
University of Warwick
Coventry
CV4 7AL
Tel: 024 765 74433
Email: M.Mannion@warwick.ac.uk
Re: Last call for 2.0.0
Posted by Gagandeep singh <ga...@gmail.com>.
Hopefully the container percolation bugs are all fixed now. So one less pain
point to worry about.
Thanks
Gagan
2010/9/1 Pablo Graña <pa...@globant.com>
> is there anyone out there planning a near future release of a site based on
> 2.0.0?
>
> On Wed, Sep 1, 2010 at 7:21 AM, Paul Lindner <li...@inuus.com> wrote:
>
> > I don't see any reason to not cut a 2.0.0 release now. Much of what's in
> > the pipeline is additive.
> >
> > I'll start the build process today if no one objects.
> >
> >
> > --
> > Paul Lindner -- lindner@inuus.com -- linkedin.com/in/plindner
> >
>
>
>
> --
> Pablo Gra\~na
> Chief Architect
> Globant
> Arg Office: +54 (11) 4109 1743
> UK Office: +44 (20) 7043 8269 int 8043
> US Office: +1 (212) 400 7686 int 8043
>
Re: Last call for 2.0.0
Posted by Michael Young <mi...@liferay.com>.
If 2.0 gets out in time, we plan to include that in our product.
- Mike
--
Liferay West Coast Symposium
September 8-9, 2010
Anaheim, CA
www.liferay.com/wcs
--
Follow us on Twitter: liferay
On Sep 1, 2010, at 3:34 AM, Pablo Graña wrote:
> is there anyone out there planning a near future release of a site based on
> 2.0.0?
>
> On Wed, Sep 1, 2010 at 7:21 AM, Paul Lindner <li...@inuus.com> wrote:
>
>> I don't see any reason to not cut a 2.0.0 release now. Much of what's in
>> the pipeline is additive.
>>
>> I'll start the build process today if no one objects.
>>
>>
>> --
>> Paul Lindner -- lindner@inuus.com -- linkedin.com/in/plindner
>>
>
>
>
> --
> Pablo Gra\~na
> Chief Architect
> Globant
> Arg Office: +54 (11) 4109 1743
> UK Office: +44 (20) 7043 8269 int 8043
> US Office: +1 (212) 400 7686 int 8043
Re: Last call for 2.0.0
Posted by Pablo Graña <pa...@globant.com>.
is there anyone out there planning a near future release of a site based on
2.0.0?
On Wed, Sep 1, 2010 at 7:21 AM, Paul Lindner <li...@inuus.com> wrote:
> I don't see any reason to not cut a 2.0.0 release now. Much of what's in
> the pipeline is additive.
>
> I'll start the build process today if no one objects.
>
>
> --
> Paul Lindner -- lindner@inuus.com -- linkedin.com/in/plindner
>
--
Pablo Gra\~na
Chief Architect
Globant
Arg Office: +54 (11) 4109 1743
UK Office: +44 (20) 7043 8269 int 8043
US Office: +1 (212) 400 7686 int 8043
Re: Last call for 2.0.0
Posted by Bastian Hofmann <ba...@googlemail.com>.
Hi,
we got one issue report regarding the generated PHP packages, which
currently don't work correctly out of the box. I could verify this
today and will have some time tomorrow to analyze and hopefully solve
this issues. So if it's okay I think we should wait a day or two, so
that we can publish a working PHP package for 2.0.
Other than that: We just released the current Shindig trunk (PHP
version) to our users at VZ.net on Monday. Considering that we
upgraded from the 1.0 release, which is I think over a year old, it
went really smooth: only four very small bugs, a few incompatiblities
in an handfull of apps and no performance problems.
In the last weeks we invested much work into optimizing our shindig
development and release process, so that we are now able to release
new snapshots of the shindig trunk (if it's stable of course) much
more frequently (even daily).
Cheers
Bastian
2010/9/1 Paul Lindner <pl...@linkedin.com>:
> Since this is a new feature they can go into trunk and we can decide later
> if they are worth merging down to a 2.0.1 or waiting for 2.1.0..
>
> I intend on getting many more releases out the door going forward.
>
> Cheers,
> Paul
>
>
> On Wed, Sep 1, 2010 at 10:55 AM, Ziv Horesh <zh...@gmail.com> wrote:
>
>> I have couple of changes I have in my pipeline for the GadgetHandler Api
>> classes (that will require correlated change in CC).
>> But I don't think I will manage to get to them this week, and I will be out
>> next week.
>>
>> -Ziv
>>
>>
>> On Wed, Sep 1, 2010 at 5:41 AM, Ciancetta, Jesse E. <jc...@mitre.org>
>> wrote:
>>
>> > I found a bug with OAuth 1.0a client support last week that I just
>> > submitted a patch for -- might be worth including it in the 2.0.0
>> release.
>> > The fix was a simple renaming of a container configuration property and
>> a
>> > few updates to the PHP code that referenced it. I submitted a JIRA issue
>> > for it here:
>> >
>> > https://issues.apache.org/jira/browse/SHINDIG-1415
>> >
>> > and code review here:
>> >
>> > http://codereview.appspot.com/2109042/
>> >
>> > --Jesse
>> >
>> > -----Original Message-----
>> > From: Paul Lindner [mailto:lindner@inuus.com]
>> > Sent: Wednesday, September 01, 2010 6:21 AM
>> > To: dev@shindig.apache.org
>> > Subject: Last call for 2.0.0
>> >
>> > I don't see any reason to not cut a 2.0.0 release now. Much of what's in
>> > the pipeline is additive.
>> >
>> > I'll start the build process today if no one objects.
>> >
>> >
>> > --
>> > Paul Lindner -- lindner@inuus.com -- linkedin.com/in/plindner
>> >
>>
>
>
>
> --
> Paul Lindner -- plindner@linkedin.com -- linkedin.com/in/plindner
>
Re: Last call for 2.0.0
Posted by Paul Lindner <pl...@linkedin.com>.
Since this is a new feature they can go into trunk and we can decide later
if they are worth merging down to a 2.0.1 or waiting for 2.1.0..
I intend on getting many more releases out the door going forward.
Cheers,
Paul
On Wed, Sep 1, 2010 at 10:55 AM, Ziv Horesh <zh...@gmail.com> wrote:
> I have couple of changes I have in my pipeline for the GadgetHandler Api
> classes (that will require correlated change in CC).
> But I don't think I will manage to get to them this week, and I will be out
> next week.
>
> -Ziv
>
>
> On Wed, Sep 1, 2010 at 5:41 AM, Ciancetta, Jesse E. <jc...@mitre.org>
> wrote:
>
> > I found a bug with OAuth 1.0a client support last week that I just
> > submitted a patch for -- might be worth including it in the 2.0.0
> release.
> > The fix was a simple renaming of a container configuration property and
> a
> > few updates to the PHP code that referenced it. I submitted a JIRA issue
> > for it here:
> >
> > https://issues.apache.org/jira/browse/SHINDIG-1415
> >
> > and code review here:
> >
> > http://codereview.appspot.com/2109042/
> >
> > --Jesse
> >
> > -----Original Message-----
> > From: Paul Lindner [mailto:lindner@inuus.com]
> > Sent: Wednesday, September 01, 2010 6:21 AM
> > To: dev@shindig.apache.org
> > Subject: Last call for 2.0.0
> >
> > I don't see any reason to not cut a 2.0.0 release now. Much of what's in
> > the pipeline is additive.
> >
> > I'll start the build process today if no one objects.
> >
> >
> > --
> > Paul Lindner -- lindner@inuus.com -- linkedin.com/in/plindner
> >
>
--
Paul Lindner -- plindner@linkedin.com -- linkedin.com/in/plindner
Re: Last call for 2.0.0
Posted by Ziv Horesh <zh...@gmail.com>.
I have couple of changes I have in my pipeline for the GadgetHandler Api
classes (that will require correlated change in CC).
But I don't think I will manage to get to them this week, and I will be out
next week.
-Ziv
On Wed, Sep 1, 2010 at 5:41 AM, Ciancetta, Jesse E. <jc...@mitre.org> wrote:
> I found a bug with OAuth 1.0a client support last week that I just
> submitted a patch for -- might be worth including it in the 2.0.0 release.
> The fix was a simple renaming of a container configuration property and a
> few updates to the PHP code that referenced it. I submitted a JIRA issue
> for it here:
>
> https://issues.apache.org/jira/browse/SHINDIG-1415
>
> and code review here:
>
> http://codereview.appspot.com/2109042/
>
> --Jesse
>
> -----Original Message-----
> From: Paul Lindner [mailto:lindner@inuus.com]
> Sent: Wednesday, September 01, 2010 6:21 AM
> To: dev@shindig.apache.org
> Subject: Last call for 2.0.0
>
> I don't see any reason to not cut a 2.0.0 release now. Much of what's in
> the pipeline is additive.
>
> I'll start the build process today if no one objects.
>
>
> --
> Paul Lindner -- lindner@inuus.com -- linkedin.com/in/plindner
>
RE: Last call for 2.0.0
Posted by "Ciancetta, Jesse E." <jc...@mitre.org>.
I found a bug with OAuth 1.0a client support last week that I just submitted a patch for -- might be worth including it in the 2.0.0 release. The fix was a simple renaming of a container configuration property and a few updates to the PHP code that referenced it. I submitted a JIRA issue for it here:
https://issues.apache.org/jira/browse/SHINDIG-1415
and code review here:
http://codereview.appspot.com/2109042/
--Jesse
-----Original Message-----
From: Paul Lindner [mailto:lindner@inuus.com]
Sent: Wednesday, September 01, 2010 6:21 AM
To: dev@shindig.apache.org
Subject: Last call for 2.0.0
I don't see any reason to not cut a 2.0.0 release now. Much of what's in
the pipeline is additive.
I'll start the build process today if no one objects.
--
Paul Lindner -- lindner@inuus.com -- linkedin.com/in/plindner