Hi Scott, To overcome the same-origin limitation, a widget has to proxify urls it wants to access so that they are served by the Wookie server.
From what we saw, proxify 'simply' calls the Wookie Proxy servlet with the target url as parameter. Wookie than handles the connection with the server and returns the content. What about cookies? If the remote url I want to reach relies on cookie, those won't be sent, and thus, the remote service won't work properly. It is by design or by default that this is not handled? Another issue with this approach is that if in the reply from the remote service there are links, those won't be proxified, thus when I click on a button, it will invoke directly the remote site, without going through wookie, Aren't we facing the same-origin limitation? Thanks for sharing your views on this Cheers Jean-Noël
