On Wed, Jun 12, 2013 at 07:00:25AM -0400, Ryan Baxter wrote: > We would appreciate a patch for sure but maybe the easiest thing to do > before going that path is to see if Google would be willing to open > source that JavaScript to Shindig. This would allow you to continue > to use you existing container while you look into transitioning to the > new common container in Shindig 2.5.
This would indeed be highly preferable, if it's possible. The JavaScript itself is very simple but it is dynamically generated server-side according to the XML document provided. Even if Google is willing to open source the server-side component, I'm not sure what type of platform/container this would need to run on. If it's an App Engine application, for example, it would be really simple to deploy an instance for our own needs. Otherwise, I'm not sure. If migrating to 2.5 would solve this problem, it might be worth-while exploring that as an alternative, depending on how much time it would cost. > Paul is this something you might be able to help with? I'll await further response. Thanks in advance for your time! Best Regards, Charl -- Charl van Niekerk ICT Service Centre University of Twente
