Ryan Baxter wrote:
I think it is important we get the fix in because we want to follow the
spec,
but I am weary of breaking things even if it is a small number of clients.
Could
we perhaps introduce a config parameter to turn this on (leaving it off by
default) and then in a later
+1
-Original Message-
From: pmlind...@gmail.com [mailto:pmlind...@gmail.com] On Behalf Of
Paul Lindner
Sent: Friday, August 09, 2013 7:39 PM
To: dev@shindig.apache.org
Subject: [VOTE] New PMC Chair Ryan Baxter
I'm officially resigning as Shindig PMC Chair. Lucky for us Ryan Baxter
has
+1
-Original Message-
From: Henry Saputra [mailto:henry.sapu...@gmail.com]
Sent: Wednesday, May 09, 2012 5:11 PM
To: dev@shindig.apache.org; us...@shindig.apache.org
Subject: [VOTE] Removing the opensocial-0.6, opensocial-0.7 and opensocial-
0.8 features from Shindig trunk
Hi Shindig
answered your question, but figured I would throw
in my 2 cents anyways. :)
Thanks,
-Stanton
From: Ciancetta, Jesse E. jc...@mitre.org
To: dev@shindig.apache.org dev@shindig.apache.org,
Date: 04/25/2012 07:44
Subject:Shindig HttpFetcher
Hi All,
We're running into an issue with our
Hi All,
We're running into an issue with our HttpFetcher implementation where slow
responses to outgoing HTTP requests are crashing our shindig server. Every
once in a great while one of the services our gadgets call on for data will
have some kind of issue and start returning really slowly
+1 for attic.
--Jesse
-Original Message-
From: Henry Saputra [mailto:henry.sapu...@gmail.com]
Sent: Wednesday, April 18, 2012 7:02 PM
To: dev@shindig.apache.org; us...@shindig.apache.org
Subject: [VOTE] Vote the fate of PHP part of Apache Shindig after 2.5.0
release
Hi Shindig
) but I think we should ensure that its
possible for implementers to do what we're doing in Rave and have it work
without needing to host a proxy on the container domain.
From: Ciancetta, Jesse E. jc...@mitre.org
To: dev@shindig.apache.org dev@shindig.apache.org,
Date: 03/27/2012 08:03 AM
+1
LGTM
Thanks Paul and Henry.
-Original Message-
From: Henry Saputra [mailto:henry.sapu...@gmail.com]
Sent: Monday, March 26, 2012 2:26 PM
To: dev@shindig.apache.org
Subject: [VOTE] Apache Shindig release 2.5.0-beta1
Hi All,
Paul Lindner has prepared a release candidate for Shindig
I've been meaning to respond to this thread for a while but have been heads
down on another project...
Another option is to embed all of the data that common container usually tries
to fetch via XHR directly into the initial response of your container page.
That's the way we do it in Rave and
And you also need to be sure to select the radio option for:
Grant license to ASF for inclusion in ASF works
when uploading the patch -- otherwise we can't legally apply it. It doesn’t
look like you did that when attaching the current patch to the JIRA ticket.
Sorry for the extra hoops to
Thanks for the patch! :)
-Original Message-
From: daviesd [mailto:davi...@oclc.org]
Sent: Wednesday, March 21, 2012 3:11 PM
To: dev@shindig.apache.org
Subject: Re: Review Request: Fix for SHINDIG-1736
Thanks for the newbie info. :)
On 3/21/12 2:34 PM, Ciancetta, Jesse E. jc
enhancements to improve
embedding and extending shindig-server (for Apache Rave)
On 02/03/2012 05:56 PM, Ciancetta, Jesse E. wrote:
Hi Ate,
I've spent some time today trying to replicate the changes in your patch in
my own local repository and so far haven't had much luck.
Ugh, I'm sorry for the trouble I
embedding and extending shindig-server (for Apache Rave)
On 01/27/2012 02:21 PM, Ciancetta, Jesse E. wrote:
Thanks Ate for taking the time to submit such a thorough proposal.
This all sounds good to me -- please submit the patch for review.
Cool, will do.
Ate
--Jesse
-Original Message
-Original Message-
From: Brian Lillie [mailto:brian...@us.ibm.com]
Sent: Tuesday, January 31, 2012 4:52 PM
To: dev@shindig.apache.org
Subject: makeRequest with 0 refresh interval
There seems to me to be a mismatch in expectations between gadget and
server if the makeRequest REFRESH param
I've been working with Ate on the Rave project since its inception and
personally have 100% trust in his opinions and recommendations on these types
of matters (and many other matters as well). Ate has been helping Rave work
though these same type of issues from the start and he's been active
Thanks Ate for taking the time to submit such a thorough proposal.
This all sounds good to me -- please submit the patch for review.
--Jesse
-Original Message-
From: Ate Douma [mailto:a...@douma.nu]
Sent: Tuesday, January 24, 2012 9:29 PM
To: dev@shindig.apache.org
Cc:
-Original Message-
From: Ate Douma [mailto:a...@douma.nu]
Sent: Friday, January 27, 2012 9:55 AM
To: dev@shindig.apache.org
Subject: Re: NOTICE and LICENSE files
On 01/27/2012 01:57 PM, Ciancetta, Jesse E. wrote:
I've been working with Ate on the Rave project since its inception
Hmm... Looks like I don’t have the proper role in Shindig JIRA to be able to
resolve tickets I didn’t submit.
Could someone with administrative privileges over the Shindig JIRA project
please grant me the needed privileges?
Thanks!
--Jesse
-Original Message-
From: Jesse Ciancetta
Hi Henry,
Thanks for taking a look.
It looks like Dan has started to pull the moduleId changes into the security
token related patch he's already been working on -- and after chatting with him
a bit this morning we've agreed that it makes sense to continue down that path.
--Jesse
to
do.
But that check should rely on the container changes I've been making as
well.
From: Ciancetta, Jesse E. jc...@mitre.org
To: dev@shindig.apache.org dev@shindig.apache.org,
Date: 12/14/2011 04:32 PM
Subject:RE: CommonContainer token refresh changes
-Original Message
-Original Message-
From: Ronny Roeller [mailto:rroel...@gmail.com]
Sent: Thursday, December 15, 2011 6:04 PM
To: dev@shindig.apache.org
Subject: Authorization for REST API
Hi,
I want to add fine-granular authorization for calls to the REST API. For
example: a) users can read all fields
-Original Message-
From: Ciancetta, Jesse E. [mailto:jc...@mitre.org]
Sent: Wednesday, December 14, 2011 1:56 PM
To: dev@shindig.apache.org
Subject: RE: CommonContainer token refresh changes
snip
Here is a quick and simplified rundown of our rendering process:
-- An HTTP request comes
-Original Message-
From: Dan Dumont [mailto:ddum...@us.ibm.com]
Sent: Monday, December 12, 2011 2:21 PM
To: dev@shindig.apache.org
Subject: Re: CommonContainer token refresh changes
Wow that didn't keep any of my formatting. Let me clean some of that up.
Our concerns are:
* The
/method for doing async js tests?
Ciancetta, Jesse E. jc...@mitre.org wrote on 12/14/2011 09:09:09 AM:
From: Ciancetta, Jesse E. jc...@mitre.org
To: dev@shindig.apache.org dev@shindig.apache.org,
Date: 12/14/2011 09:10 AM
Subject: RE: CommonContainer token refresh changes
-Original
on that in the response I
just sent to Dan in another thread.
- Henry
On Wed, Dec 14, 2011 at 6:09 AM, Ciancetta, Jesse E. jc...@mitre.org
wrote:
-Original Message-
From: Dan Dumont [mailto:ddum...@us.ibm.com]
Sent: Monday, December 12, 2011 2:21 PM
To: dev@shindig.apache.org
Subject: Re
-Original Message-
From: Ciancetta, Jesse E. [mailto:jc...@mitre.org]
Sent: Wednesday, December 14, 2011 9:09 AM
To: dev@shindig.apache.org
Subject: RE: CommonContainer token refresh changes
snip
* Introduce a new callback in the render chain of a gadget that will
attempt to refresh
+1
-Original Message-
From: Paul Lindner [mailto:lind...@inuus.com]
Sent: Tuesday, December 13, 2011 9:27 AM
To: dev@shindig.apache.org
Subject: Emeritus status for inactive members
Hi,
I'd like to suggest that people 2y inactive on Shindig move to Emeritus
status.
--
Paul Lindner --
Hmm -- I'm not seeing the case where what your describing could happen.
If I understand what you're saying -- it sounds like content is being written
directly to the response object, and if an exception is thrown after the
response buffer has already been flushed then at that point it's too
-Original Message-
From: Ryan J Baxter [mailto:rjbax...@us.ibm.com]
Sent: Tuesday, November 22, 2011 9:15 PM
To: dev@shindig.apache.org
Subject: Re: [VOTE] Release shindig 3.0.0 beta4...
I am not sure if this is a -1 but I am seeing some problems with some of
the functionality around
-Original Message-
From: daviesd [mailto:davi...@oclc.org]
Sent: Monday, November 28, 2011 10:38 AM
To: dev@shindig.apache.org
Subject: Re: [VOTE] Release shindig 3.0.0 beta4...
+1 (if I'm allowed to vote)
Community votes aren't officially binding -- we still need three Shindig PMC
-Original Message-
From: daviesd [mailto:davi...@oclc.org]
Sent: Tuesday, November 22, 2011 2:14 PM
To: shindig
Subject: SecurityTokenKeyFile
I know there was a change recently (SHINDIG-1636) that changed the way the
token encryption key was loaded. I use to have
-Original Message-
From: Ciancetta, Jesse E.
Sent: Tuesday, November 22, 2011 2:24 PM
To: shindig
Subject: RE: SecurityTokenKeyFile
-Original Message-
From: daviesd [mailto:davi...@oclc.org]
Sent: Tuesday, November 22, 2011 2:14 PM
To: shindig
Subject: SecurityTokenKeyFile
I know
?
- Henry
On Tue, Nov 22, 2011 at 11:42 AM, daviesd davi...@oclc.org wrote:
Ah, I didn't catch that. Sorry. Yes, changing to just securityTokenKey
works. Thanks a lot!
doug
On 11/22/11 2:36 PM, Ciancetta, Jesse E. jc...@mitre.org wrote:
-Original Message-
From: Ciancetta, Jesse E
live with updating the UPGRADING file. +1
- Henry
On Tue, Nov 22, 2011 at 12:04 PM, Ciancetta, Jesse E. jc...@mitre.org
wrote:
-Original Message-
From: Stanton Sievers [mailto:ssiev...@us.ibm.com]
Sent: Tuesday, November 22, 2011 2:56 PM
To: dev@shindig.apache.org
Subject: Re
+1
-Original Message-
From: Paul Lindner [mailto:plind...@google.com]
Sent: Wednesday, November 16, 2011 1:03 PM
To: dev@shindig.apache.org
Subject: switch to commons lang 3?
Hi,
commons-lang was upgraded recently to actually support Java 5 ('bout time!)
What do people think about
Hi Paul,
Please add me to the PMC list.
Thanks!
--Jesse
-Original Message-
From: Paul Lindner [mailto:lind...@inuus.com]
Sent: Tuesday, November 15, 2011 11:08 AM
To: dev@shindig.apache.org
Subject: PMC membership for committers
We have a policy of adding committers to the Shindig PMC
trusted domains)?
Yeah -- there were a bunch of different ideas discussed in those threads. Let
us know if you have any more specific questions.
Thanks,
Dennis
On Mon, Oct 31, 2011 at 10:53 AM, Ciancetta, Jesse E.
jc...@mitre.orgwrote:
-Original Message-
From: Dennis Ju [mailto:dennis
-Original Message-
From: Stanton Sievers [mailto:ssiev...@us.ibm.com]
Sent: Monday, October 31, 2011 8:12 AM
To: dev@shindig.apache.org
Subject: Injecting global config contributors for the default config process
Hi everyone,
I've recently been looking at the ConfigContributor and
-Original Message-
From: Dennis Ju [mailto:dennis...@liferay.com]
Sent: Monday, October 31, 2011 1:33 PM
To: dev@shindig.apache.org
Subject: Accessing protected gadgets?
Hello,
Is there a way for Shindig to access a gadget XML who's URL requires
authentication? We want to allow hosting
+1
-Original Message-
From: Henry Saputra [mailto:henry.sapu...@gmail.com]
Sent: Tuesday, October 25, 2011 1:43 PM
To: dev@shindig.apache.org
Cc: priv...@shindig.apache.org
Subject: [VOTE] Approve Li Xu as Apache Shindig PMC and Committer
Hello,
I would like to propose that Li Xu be
+1
-Original Message-
From: Henry Saputra [mailto:henry.sapu...@gmail.com]
Sent: Tuesday, October 25, 2011 1:50 PM
To: dev@shindig.apache.org
Cc: priv...@shindig.apache.org
Subject: [VOTE] Approve Stanton Sievers as Apache Shindig PMC and
Committer
Hello,
I would like to propose that
+1
-Original Message-
From: Henry Saputra [mailto:henry.sapu...@gmail.com]
Sent: Tuesday, October 25, 2011 1:47 PM
To: dev@shindig.apache.org
Cc: priv...@shindig.apache.org
Subject: [VOTE] Approve Dan Dumont as Apache Shindig PMC and Committer
Hello,
I would like to propose that Dan
-Original Message-
From: Ryan J Baxter [mailto:rjbax...@us.ibm.com]
Sent: Friday, October 21, 2011 9:00 AM
To: dev@shindig.apache.org
Subject: Release Apache Shindig Version 3.0.0-beta3
What does everyone think about releasing beta3? It has been 4 months
since we last released a beta and
.
Any ideas?
-Original Message-
From: Ciancetta, Jesse E. [mailto:jc...@mitre.org]
Sent: Thursday, October 13, 2011 5:50 AM
To: dev@shindig.apache.org
Subject: RE: Failing to connect to https server through gadget
I've run into this situation a bunch of times myself and the best way
I've
in the Provider. Even
changing the type of the config value would be trivial in this case
because the Provider gives you that layer of abstraction.
-Stanton
From: Dan Dumont/Westford/IBM@Lotus
To: dev@shindig.apache.org,
Cc: Ciancetta, Jesse E. jc...@mitre.org, Stanton
Sievers/Westford/IBM@Lotus
I've run into this situation a bunch of times myself and the best way I've
found to get to the root of the issue is to turn on low level debugging
directly in the networking API's.
Shindig is using HttpClient under the covers for all of its network fetching,
and HttpClient is using the
://reviews.apache.org/r/1632/
Thanks!
-Original Message-
From: Jesse Ciancetta [mailto:jc...@mitre.org]
Sent: Tuesday, October 04, 2011 1:28 PM
To: shindig; Ciancetta, Jesse E.; Stanton Sievers
Subject: Re: Review Request: Common container currently doesnt include
the
siteId (moduleId) in any
it.
Here is a link to the review for more detail:
https://reviews.apache.org/r/1632/
Thanks!
-Original Message-
From: Jesse Ciancetta [mailto:jc...@mitre.org]
Sent: Tuesday, October 04, 2011 1:28 PM
To: shindig; Ciancetta, Jesse E.; Stanton Sievers
Subject: Re: Review Request: Common
: rjbax...@us.ibm.com
Phone: 978-899-3041
developerWorks Profile
From: Ciancetta, Jesse E. jc...@mitre.org
To: dev@shindig.apache.org dev@shindig.apache.org,
Cc: Stanton Sievers/Westford/IBM@Lotus
Date: 09/30/2011 10:51 AM
Subject:RE: Review Request: Common container currently
-Original Message-
From: Ryan J Baxter [mailto:rjbax...@us.ibm.com]
Sent: Thursday, September 29, 2011 1:54 PM
To: Ciancetta, Jesse E.
Cc: dev@shindig.apache.org; Stanton Sievers
Subject: RE: Review Request: Common container currently doesnt include the
siteId (moduleId) in any of it's
and discussion from Stanton and others.
--Jesse
From: Ryan J Baxter [mailto:rjbax...@us.ibm.com]
Sent: Wednesday, September 28, 2011 5:55 PM
To: dev@shindig.apache.org; Stanton Sievers
Cc: Ciancetta, Jesse E.
Subject: Re: Review Request: Common container currently doesnt include the
siteId
Right, but from reading the shindig code, you might come to other
conclusions. Is there anyone involved with the locked domain code that is
still on this list?
I didn't write any of the Shindig locked-domain code, but I have worked with it
for our internal Shindig 2.x based deployment and will
for @Synchronized):
http://svn.apache.org/viewvc/incubator/rave/trunk/rave-portal/src/main/java/org/apache/rave/portal/service/impl/DefaultRegionWidgetService.java?view=markup
-Original Message-
From: Ciancetta, Jesse E.
Sent: Wednesday, September 14, 2011 11:11 AM
To: shindig; rave
developerWorks Profile
From: Ciancetta, Jesse E. jc...@mitre.org
To: dev@shindig.apache.org dev@shindig.apache.org,
Date: 09/14/2011 01:48 PM
Subject:RE: [jira] [Resolved] (SHINDIG-1580) Allow for custom
security token fetch function to be used when refreshing security tokens
Thanks
Do you use a web proxy to access the internet?
If so you need to set the proxy in the shindig.properties file - it's bundled
in the shindig*-common jar file - you can extract it and put it somewhere
closer in the classpath (/WEB-INF/classes works for Tomcat) and modify it to
include your proxy
Shindig (by default) expects to be deployed to the root context -- so try
deploying to / instead of /shindig-server-2.0.0.
If your using tomcat you can do this by just renaming the war file to ROOT.war
-Original Message-
From: Naresh Chaurasia [mailto:nc.java...@gmail.com]
Sent:
Message-
From: Henry Saputra (JIRA) [mailto:j...@apache.org]
Sent: Tuesday, September 13, 2011 8:20 PM
To: Ciancetta, Jesse E.
Subject: [jira] [Resolved] (SHINDIG-1580) Allow for custom security token
fetch function to be used when refreshing security tokens
[ https://issues.apache.org/jira
the previous message in this email thread for details on the pending
reviews.
Thanks!
-Original Message-
From: Ciancetta, Jesse E.
Sent: Thursday, September 01, 2011 9:09 AM
To: 'Ryan J Baxter'; dev@shindig.apache.org; Michael Hermanto
Subject: RE: Review Request: Allow for incremental
: Wednesday, August 31, 2011 9:26 PM
To: dev@shindig.apache.org; Michael Hermanto
Cc: Ciancetta, Jesse E.
Subject: Re: Review Request: Allow for incremental preloading of gadget
metadata and security tokens
Mike, would you mind taking a quick look like this?
-Ryan
Email: rjbax...@us.ibm.com
Phone: 978
+1
But in addition to adding the ability to set the owner/viewer and working with
caja I think we should also get the common container to use proper moduleId's
in security tokens (all security tokens in common container currently get
minted with a moduleId of 0). This will cause implementers
for
fetching appdata (which isn’t scoped to a particular gadget instance) you might
not care about moduleId's...
Thanks!
--Jesse
-Original Message-
From: Jesse Ciancetta [mailto:jc...@mitre.org]
Sent: Wednesday, August 24, 2011 10:47 AM
To: shindig; Ciancetta, Jesse E.
Subject: Review Request
16, 2011 at 11:45 AM, Ciancetta, Jesse E.
jc...@mitre.orgwrote:
Hi All,
Common container currently supports a one-time bulk preload of gadget
metadata and security tokens via the opt_config parameter passed to the
Container constructor, however it would also be useful to have a way
Hi All,
Common container currently supports a one-time bulk preload of gadget metadata
and security tokens via the opt_config parameter passed to the Container
constructor, however it would also be useful to have a way to incrementally
preload this data as well.
We're currently doing this in
Thanks Henry and Paul!
I've gone ahead and closed out the review request as submitted.
-Original Message-
From: Henry Saputra [mailto:henry.sapu...@gmail.com]
Sent: Friday, August 12, 2011 10:55 PM
To: dev@shindig.apache.org
Subject: Re: Review Request: Enable loading security token key
it (and now
implementing it). In our case a particular gadget always renders in the
same
siteid. Two instances of the same gadget would have different siteids,
thus
different preferences.
doug
On 7/28/11 11:51 AM, Ciancetta, Jesse E. jc...@mitre.org wrote:
If you wish to persist preferences
suspiciously akin to the functionality
already present in exportJs(...) used for exporting symbols. This method
upserts the namespace in much the same way as your helper method does.
Thoughts on whether we could reuse or augment that?
-j
On Thu, Jul 28, 2011 at 7:52 AM, Ciancetta, Jesse E. jc
I agree with John -- I also prefer the first style Paul presented (which I
believe is also the most prevalent style in Shindig currently).
With respect to the issues that Michael raised about building up a namespace
from across different files -- this got me thinking about a little namespace
If you wish to persist preferences for a particular occurrence of a
gadget(per gadget url instance), then you'll need to keep track of the
site (the auto generated ids are less helpful), if you wish to provide
per gadget url preferences you can just ignore they siteid and return or
persist the
I believe appdata is stored per user/per application as opposed to per user/per
application instance, so I think you'll need to add the module ID (application
instance ID) somewhere in your naming scheme for the persisted appdata.
I think as its implemented currently two instances of the same
So with some research it looks like I'm supposed to be implementing my own
server module. Is that pretty much accurate?
Yes -- you'll need to implement both the client side UI for editing preferences
and the server side API for persisting them. I actually just did that work
though for the
We've moved our dependency to 3.0.0-beta2 and its working well.
Thanks for getting this done Paul -- it's much appreciated!
-Original Message-
From: Paul Lindner [mailto:lind...@inuus.com]
Sent: Monday, June 13, 2011 9:06 PM
To: dev@shindig.apache.org
Subject: [RESULT] Release Apache
Paul Lindner sent a message about this a few weeks back -- sounds like nix is
gone for good:
http://markmail.org/message/cws5x6wbtpwrgt2a
-Original Message-
From: Maruti Dattatreya [mailto:maruti.dattatr...@db.com]
Sent: Thursday, May 05, 2011 4:03 AM
To: dev@shindig.apache.org
Subject:
-Original Message-
From: Davies,Douglas [mailto:davi...@oclc.org]
Sent: Thursday, March 31, 2011 5:27 PM
To: dev@shindig.apache.org
Subject: RE: Shindig and webapp on same host/domain or not?
Isaiah,
Were you successful on getting this to work? I tried a similar approach
today using
is running over https, and i can not
find a option to use https instead of http, could you give me a way
here?
Thanks.
De: Ciancetta, Jesse E. [jc...@mitre.org]
Enviado: terça-feira, 1 de fevereiro de 2011 13:20
Para: us...@shindig.apache.org; dev
Hi Thorsten,
We just released our Java based container to:
http://code.google.com/p/osec/
Our immediate goal for the project was to replace our heavy-weight commercial
portal product, so we don't have profile pages or any of the more social
aspects of Partuza in this release, but we do plan
You can disable content rewriting globally by editing shindig.properties and
moving the wildcard value from shindig.content-rewrite.include-urls to
shindig.content-rewrite.exclude-urls -- so you end up with this configuration:
shindig.content-rewrite.include-urls=
If there's nothing sensitive in the gadget specs that need authentication on a
per user basis, you could probably just guice inject a custom extended version
of the BasicHttpFetcher which overrides the fetch method and looks at the URI
of the resource being fetched -- and if it's a request for
I think the reason the iframe src gets set to about:blank is to work around an
issue with the bfcache (back-forward cache) in some browsers -- have a look at
the comments for this JIRA issue for a detailed discussion:
https://issues.apache.org/jira/browse/SHINDIG-158
The iframe disappearing
You shouldn't need to provide your own guice modules to use customized versions
of shindig.properties and container.js -- if you just put your customized
copies under /your-shindig-app/WEB-INF/classes they'll end up in the classpath
ahead of the versions bundled in the shindig-common jar. I'll
Hi Nuwan,
I'm wondering if a servlet filter might be a possible solution to this problem.
Since it sounds like everything is running under the same servlet container, I
think you could just drop a servlet filter in front of any /gadgets/ifr
requests and within the filter get access to the
Hi,
I noticed that it doesn't appear that people are using the concat and proxy
servlets in the wild and I was wondering if anyone might be able to provide any
insight into why that is. I looked at all the resources loaded for an iframed
gadget on LinkedIn, iGoogle and a local instance of
+1 (non-binding)
-Original Message-
From: Paul Lindner [mailto:lind...@inuus.com]
Sent: Friday, August 20, 2010 1:46 AM
To: dev@shindig.apache.org
Subject: [VOTE] Approve Gagandeep singh as Shindig Committer
I would like to propose that Gagandeep Singh be granted committer
access to
://codereview.appspot.com/.
This would help the shindig community review it better.
On Wed, Aug 18, 2010 at 1:49 AM, Ciancetta, Jesse E. jc...@mitre.orgwrote:
I ran into another container configuration related issue while testing out
RC2, which is that the CSS rewriter doesn't seem to be taking the container
[mailto:fa...@google.com]
Sent: Monday, August 16, 2010 5:32 PM
To: dev@shindig.apache.org
Subject: Re: [VOTE] Release Apache Shindig Version 2.0.0-RC2
What are your configured values for keys
gadgets.uri.proxy.host
gadgets.uri.proxy.path
?
On Mon, Aug 16, 2010 at 1:13 PM, Ciancetta, Jesse E
passed in null to trigger the default
behavior (which is to return the default container).
I uploaded the patch file (which I based against the RC2 sources) to JIRA here:
https://issues.apache.org/jira/browse/SHINDIG-1411
--Jesse
-Original Message-
From: Ciancetta, Jesse E. [mailto:jc
Hi,
I spent some time this morning trying to test out the RC2 build and ran into an
issue trying to define additional containers (our internal implementation
defines additional containers beyond default and I was trying to get that
working). As a test I defined a new container called foo and
Hi Johan,
There's an auth-refresh feature that ships with Shindig that sounds like it
should help here. You can find more info on it here:
http://markmail.org/message/c2ixtrlqrvyt3tgg
and here:
https://issues.apache.org/jira/browse/SHINDIG-655
Hope that helps!
--Jesse
-Original
87 matches
Mail list logo
