Hi Dennis,
I submitted a defect to Open Ajax bug tracker, as you requested (ID: 3479818, https://sourceforge.net/tracker/?func=detail&atid=874168&aid=3479818&group_id=175671). Please let me know what I should expect next. Thanks, Ilya From: Dennis Ju [mailto:dennis...@liferay.com] Sent: Wednesday, January 25, 2012 4:17 PM To: Shtein, Ilya Cc: dev@shindig.apache.org Subject: Re: Shindig 3.0 timeline Hi Ilya, Your fix looks good, but my concern is that the code change is for OpenAjax Hub's iframe.js. Ideally, we would patch it in OpenAjax's repo and bring in the patched version to Shindig's trunk. Otherwise any patch will be lost when Shindig updates OpenAjax Hub (which should be done anyways since 2.0.7 is out and Shindig is on 2.0.5). Are you able to create an issue (per your company's policies) on OpenAjax's bug tracker (link<http://sourceforge.net/tracker/?group_id=175671&atid=874168>)? If not, I can do it. Once it's patched there, I can create a patch for Shindig. Also, what version of Shindig are you testing against? Looking at current trunk's rpc.js changes, it appears that the code changes Maxwell and I suggested in SHINDIG-1497 are no longer necessary in Shindig 3.x, but I haven't tested it myself yet. Thanks, Dennis On Wed, Jan 25, 2012 at 11:48 AM, Shtein, Ilya <ilya.sht...@fisglobal.com<mailto:ilya.sht...@fisglobal.com>> wrote: My company discourages contributing to open source, so I contributed my fix indirectly by submitting a comment to Dennis's original post. The SHINDIG-1497 issue consists of two parts: - exceptions when moving pubsub-2 gadget's IFrame in the DOM tree - problem with multiplying number of subscriptions when dropping a pubsub-2 gadget My patch takes care of the second issue; Dennis seems to have an idea how to fix the first one (I myself had to use both changes suggested in the discussion between Dennis and Maxwell Chiareli). Or, perhaps the original contributors of pubsub-2 code (Javier Pedemonte, Han Nguyen?) could chime in on what the best route is. Anyway, I give my permission to whoever prepares a patch for SHINDIG-1497 to use the fix I suggested, and hope the issue will be fixed in the upcoming Shindig release. Thanks, Ilya From: Ryan J Baxter [mailto:rjbax...@us.ibm.com<mailto:rjbax...@us.ibm.com>] Sent: Tuesday, January 24, 2012 8:52 PM To: dev@shindig.apache.org<mailto:dev@shindig.apache.org> Subject: RE: Shindig 3.0 timeline Ilya, if you or Dennis want to investigate and come up with a patch to support this use case, we are happy to accept it :) Everyone on the dev list would be happy to help you or anyone else through the process of writing the patch and getting it committed. Regards, RYAN J. BAXTER Software Engineer - OpenSocial IBM Collaboration Solutions ________________________________ Phone: 1-978-899-3041<tel:1-978-899-3041> E-mail: rjbax...@us.ibm.com<mailto:rjbax...@us.ibm.com> Blog: ryanjbaxter.com<http://ryanjbaxter.com/> Chat: rbaxter85 ryanjasonbaxter Find me on: and within IBM on: <http://www.linkedin.com/in/ryanjbaxter> 550 King St Littleton, MA 01460-1250 United States From: "Shtein, Ilya" <ilya.sht...@fisglobal.com> To: "dev@shindig.apache.org" <dev@shindig.apache.org>, Date: 01/20/2012 10:12 AM Subject: RE: Shindig 3.0 timeline ________________________________ Any chance SHINDIG-1497 will be fixed in 3.0.0 (https://issues.apache.org/jira/browse/SHINDIG-1497)? How can a new version be released with such an important feature (pubsub-2) in a broken state? I am not allowed to contribute, but will be happy to provide information to anyone who is willing to work on it. Thanks, Ilya -----Original Message----- From: Paul Lindner [mailto:lind...@inuus.com] Sent: Friday, January 20, 2012 8:55 AM To: dev@shindig.apache.org Subject: Re: Shindig 3.0 timeline I'm not keen on version numbers myself. We can release at any time really, code is stable, tests are all green. If someone wants to sign up to do maint releases of 3.0.x that would be helpful. Vote: Release current trunk as shindig-3.0.0, move trunk to 3.1.0-SNAPSHOT [ ] +1 do it [ ] +0 meh [ ] -1 I have just one more patch. If you do -1 please provide code-review links or jira issues you consider blockers for 3.0.0 On Fri, Jan 20, 2012 at 3:51 AM, Derek Houghton <de...@chuwori.co.uk> wrote: > Hi, > Didn't catch a reply to this? > Could you tell me when stable shindig 3.0 is due for public release? > > Thanks > Derek > > > On 16 Jan 2012, at 10:57, Evgeny Bogdanov wrote: > > > Hello, > > > > when the shindig 3.0 is due? > > > > Best > > Evgeny > > -- Paul Lindner -- lind...@inuus.com -- profiles.google.com/pmlindner _____________ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _____________ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.<http://www.linkedin.com/in/ryanjbaxter> <http://www.linkedin.com/in/ryanjbaxter> <http://www.linkedin.com/in/ryanjbaxter> -- Nordic Symposium 25 April 2012 Register today: www.liferay.com/nordic2012<http://www.linkedin.com/in/ryanjbaxter> _____________ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
