It seems that this is something related to javascript + security limitations, as a script can't target a page that is not on the same (sub-?)domain. Halas, I don't clearly identify this problem and i'm still not sure about it.
This technology seems very promising but there is a major problem with the architectural design if that separation can't be done. Denis Valdenaire On 6 jan, 16:55, Denis Valdenaire <[email protected]> wrote: > Hello, > > I made a prototype that works and now i'm trying to design the final > architecture. Is it possible to have the ape server (listening on > 6969) on one host, and the ape-jsf server (serving only the static > HTML page) on another host ? > > I tried to configure that way, but it failed, and i failed also to > clearly understand why. > > The client call a page on the ape-jsf server : it got HTML + > javascript executed. > The client, then, call the real ape server on port 6969 (and got > nothing more to do with the previous one, right ?) > > Well, the fact is, when i run Tools/Check, i got the following error : > > Running test : Contacting APE Server > Can't contact APE Server. Please check the your APE Server is running > and the folowing url is pointing to your APE server > :http://ape.mydomain.fr:6969 > > Did i miss somehting ? > > Thanks a lot for your help.
-- You received this message because you are subscribed to the Google Groups "APE Project" 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/ape-project?hl=en --- APE Project (Ajax Push Engine) Official website : http://www.ape-project.org/ Git Hub : http://github.com/APE-Project/
