[EMAIL PROTECTED] is probably the better place to send
that, however I'm flattered to see chabotc.com has a pertinent place
in your copy and paste buffer? :-)
On Jul 8, 2008, at 10:36 PM, Cassie wrote:
+ Astha directly
Astha - Should we give you credit for this patch? :)
- Cassie
On Tue, Jul 8, 2008 at 1:24 PM, Chris Chabot <[EMAIL PROTECTED]>
wrote:
If I'm not mistaking the mystery man is:
"I am a technical lead/architect working with Impetus technologies (
http://www.impetus.com). I lead a group of 15 R&D engineers who are
dedicated to work on Social networking and OpenSocial activities. We
(Impetus) have been actively involved with OpenSocial activities
since it
was announce in Nov 2007. As a part of that the current team is
working on
Shindig Java and PHP projects." - Astha Bhatnagar <
[EMAIL PROTECTED]>
:-)
-- Chris
On Jul 8, 2008, at 9:58 PM, Cassie wrote:
Just as a btw - it would be good to get the real name of whoever is
filing
bugs as "impetus technologies". Without your real name when I
submit this
patch the commit won't be associated with your good deeds. So even
if you
start participating on the mailing list and submit the most glorious
patches
we will never be able to welcome you as a committer :(
Hope to hear from you soon...
- Cassie
On Tue, Jul 8, 2008 at 5:46 AM, impetus technologies (JIRA) <
[EMAIL PROTECTED]
wrote:
[
https://issues.apache.org/jira/browse/SHINDIG-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
impetus technologies updated SHINDIG-432:
-----------------------------------------
Attachment: samplecontainer.html.patch
samplecontainer.html generate incorrect security token when the
gadget
url is changed and the user clicks reset
---------------------------------------------------------------------------------------------------------------
Key: SHINDIG-432
URL: https://issues.apache.org/jira/browse/
SHINDIG-432
Project: Shindig
Issue Type: Bug
Components: Sample container & Examples
Environment: Windows, Apache
Reporter: impetus technologies
Attachments: samplecontainer.html.patch
The new security token which is generated takes the previous url
which
results into wrong security token. Patch is attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
