On Wed, Jun 25, 2008 at 4:24 PM, Chris Chabot <[EMAIL PROTECTED]> wrote:

> On Jun 26, 2008, at 1:14 AM, Kevin Brown wrote:
>
>  On Wed, Jun 25, 2008 at 3:39 PM, Chris Chabot <[EMAIL PROTECTED]> wrote:
>>
>>  So how do you do your per-container config in java land? (purely for the
>>> 'inject this class with guice to handle the people data service for
>>> container 'foo' and this other class for 'bar')
>>>
>>
>>
>> The social-api code isn't doing it yet -- it probably will once Cassie /
>> David / Louis / whoever else is working on there encounter the same
>> problems
>> that you have (security token decryption is the most obvious one).
>>
>> The gadgets code uses
>>
>> http://svn.apache.org/viewvc/incubator/shindig/trunk/java/gadgets/src/main/java/org/apache/shindig/gadgets/ContainerConfig.java?view=markup
>>
>> We'll probably hoist this up into common so that both gadgets + social-api
>> can use it.
>>
>
> yep on the gadgets side it's easy enough since you always have the
> container key. In the proxy server it's already a bit trickier, there's no
> container key in the url / post body there, and yet the config determines
> what http content fetcher to use. On the social side you have no container
> key (that's accessible before having a token class, which is config based)
> to know which service handlers to use.


I was actually going to add container to the proxied calls anyway, which
makes it a lot easier to deal with certain aspects of content rewriting and
http error reporting.


>
>
> It's an interesting problem indeed :)
>
> Adding &container=foo seems to be the only logical solution so far then
>
>        -- Chris
>

Reply via email to