I was wondering if it would be ok to add a &container=foo param to the
social requests.
I've been working on restructuring the configuration system for PHP
shindig, and one of my goals is to make a per-container server config
(as is already possible for the javascript configuration in shindig/
config/<container>.js).
I would like to mimic the same kind of setup in PHP, and load the
default + container specific config for each social data request, so
that the data services etc are also configurable per container.. that
way you can truly have one shindig instance do it's thing for multiple
social sites.
Now my initial thought was to use the security token for this (the
domain key), however there's a catch 22 in that, and that is that the
token decoder is also a configurable class ... so it's not available
before the config is loaded, and hence the catch 22 :)
So either i have to let go of my plan to make a per-container config
for php shindig, or add the un-encoded container param to the requests.
What do you guys reckon?
-- Chris
