On Mon, 31 May 2010, Qoo Goo wrote:
> Haha, interesting discussion. Yes. If you do not flushes data before..
> I've seen these past days people out there saying (it's easy to find
> it googling) that the correct way to do things is:
>
> Response.Flush()
> Response.Close()
> Response.End()
A 100'0
2010/5/31 Derrell Lipman :
> On Mon, May 31, 2010 at 13:36, Qoo Goo wrote:
>>
>> 2010/5/31 Derrell Lipman :
>>
>> Yes, I agree. It's not the same calling a Response.End() than calling
>> Response.Close(), for sure (I must admit that I haven't never used
>> this method, I have to catch up who was!!
On Mon, May 31, 2010 at 13:36, Qoo Goo wrote:
> 2010/5/31 Derrell Lipman :
>
> Yes, I agree. It's not the same calling a Response.End() than calling
> Response.Close(), for sure (I must admit that I haven't never used
> this method, I have to catch up who was!!). In fact, quoting VS
> built-in me
2010/5/31 Derrell Lipman :
> On Mon, May 31, 2010 at 09:16, Qoo Goo wrote:
>>
>> Hi Derrell and everyone,
>>
>> We've been able to solve the problem. It was one of those kind of
>> extremely silly problems that sometimes are hard to find. I post the
>> explanation here just to prevent others (we'v
On Mon, May 31, 2010 at 09:16, Qoo Goo wrote:
> Hi Derrell and everyone,
>
> We've been able to solve the problem. It was one of those kind of
> extremely silly problems that sometimes are hard to find. I post the
> explanation here just to prevent others (we've lost almost two days of
> work!).
Hi Derrell and everyone,
We've been able to solve the problem. It was one of those kind of
extremely silly problems that sometimes are hard to find. I post the
explanation here just to prevent others (we've lost almost two days of
work!).
I was just that we were closing the socket in server side.
On Thu, May 27, 2010 at 15:57, Qoo Goo wrote:
> 2010/5/27 Derrell Lipman :
> > Unfortunately, there's not a lot that qooxdoo can do to help you with
> this.
> > My suggestion would be to use wireshark or some similar protocol
> analyzer,
> > and look at exactly what packets are going back and for
2010/5/27 Derrell Lipman :
> On Thu, May 27, 2010 at 14:08, Qoo Goo wrote:
>>
>> Hi everybody,
>>
>> We are facing a problem with Chrome 5 (5.0.375.55) that is driving us
>> crazy.
>>
>> We have an application that has been working since now in main
>> browsers, including IE 5 to 8, FF and Chrome.
On Thu, May 27, 2010 at 14:08, Qoo Goo wrote:
> Hi everybody,
>
> We are facing a problem with Chrome 5 (5.0.375.55) that is driving us
> crazy.
>
> We have an application that has been working since now in main
> browsers, including IE 5 to 8, FF and Chrome. We are migrating the app
> to Qx 1.1
