Thanks for all your answers.. I overthought your ideas and in the end I
decided to use mod_mono on the same host. Seems to be way more stable
than xsp2.
Regards, Tim
Helder Magalhães wrote:
>
> Derrell Lipman wrote:
>> Whenever you attempt to work with multiple ports or servers, you're
>> aski
Derrell Lipman wrote:
>
> Whenever you attempt to work with multiple ports or servers, you're
> asking for trouble.
>
Derrel is right. Using different ports will force you to use «special
tricks»... The proxy approach seems allot more cleaner and likely to work
better in the future (browser's
On Feb 6, 2008 7:45 AM, Alex Back <[EMAIL PROTECTED]> wrote:
> Hi Tim,
>
> Tim Taubert wrote:
> > Hi,
> > I have the following scenario:
> >
> > My Qooxdoo app is accessible via http://localhost/. From there I want to
> > access a Mono/ASP.NET service running on localhost:8080.
> I think you run in
Hi Tim,
Tim Taubert wrote:
> Hi,
> I have the following scenario:
>
> My Qooxdoo app is accessible via http://localhost/. From there I want to
> access a Mono/ASP.NET service running on localhost:8080.
I think you run into an error concerning the "Same origin policy" [1]. It is
not allowed to cal
Hi,
I have the following scenario:
My Qooxdoo app is accessible via http://localhost/. From there I want to
access a Mono/ASP.NET service running on localhost:8080.
Every time I use qx.io.remote.Rpc firebug is displaying this error:
"172595 ERROR: qx.io.remote.Exchange[468]: Request handler thro
