Thanks Larry, and sorry for being late with my feedback. Larry Kluger wrote: > Hi, > > Good job. > > I suggest that you give each group their own webserver. Or use a CMS > so each group can control its own destiny. Remember that you can > easily host multiple web servers (one per group/department) on one > physical server.
OK. I think it won't be a problem. I can create virtual servers. > > Note that you can have the Javascript library on a different domain. > The issue is that the original html page loaded by your users into the > browser must have the same root domain name as the datafile loaded by > the Timeline library. Usually this not a problem since the html file > goes along with the datafile. In our case the datafile is generated on the fly from a blog/wiki environment. So, they don't travel along with the html file. Something like this... http://xepecnet.environmentalchange.net/xwiki/bin/view/ICT/xmlPdR?xpage=rdf > > There are some ways to work-around the same origin policy, but they > are all messy and complicated to set up. Google for solutions if you > wish to know more. I will first of all to solve some other issues without facing the "same origin policy" problem. As we are facing a new era in software developement where the API is exposed in a remote site, it doesn't much sense for me not to be able to load data from another remote location. I will keep this thread posted! Cheers, Ricardo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SIMILE Widgets" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/simile-widgets?hl=en -~----------~----~----~----~------~----~------~--~---
