Re: [qooxdoo-devel] qx.io.remote.Request queued but not queued and qooxdoo hangs

Hi, Dietrich. On Thu, Oct 22, 2015 at 2:48 AM, Dietrich Streifert < dietrich.streif...@googlemail.com> wrote: > Hi Kenneth, > > would you mind sending you (asuming) qx.ui.table.model.Remote based > class to the list, so we can study what might be the problem? > Thx. Attached. Here is the code fo

Re: [qooxdoo-devel] qx.io.remote.Request queued but not queued and qooxdoo hangs

om: Kenneth Tilton > Reply-To: qooxdoo Development > Date: Wednesday, 21 October 2015 at 20:12 > To: qooxdoo Development > Subject: Re: [qooxdoo-devel] qx.io.remote.Request queued but not queued > and qooxdoo hangs > > And now we descend into the rabbit hole: > > The stude

Re: [qooxdoo-devel] qx.io.remote.Request queued but not queued and qooxdoo hangs

Hi Kenneth, would you mind sending you (asuming) qx.ui.table.model.Remote based class to the list, so we can study what might be the problem? Am 21.10.2015 um 21:12 schrieb Kenneth Tilton: > And now we descend into the rabbit hole: > > The students on which the request hangs are the only ones wi

Re: [qooxdoo-devel] qx.io.remote.Request queued but not queued and qooxdoo hangs

? Regards John. From: Kenneth Tilton Reply-To: qooxdoo Development Date: Wednesday, 21 October 2015 at 20:12 To: qooxdoo Development Subject: Re: [qooxdoo-devel] qx.io.remote.Request queued but not queued and qooxdoo hangs And now we descend into the rabbit hole: The students on which

Re: [qooxdoo-devel] qx.io.remote.Request queued but not queued and qooxdoo hangs

And now we descend into the rabbit hole: The students on which the request hangs are the only ones with 17 rows of data. It is the count that corrupts things, not the data, and I can unhang the student by adding or removing data or just by lying when I call _onLoadRowCount and passing 18 if the tr

Re: [qooxdoo-devel] qx.io.remote.Request queued but not queued and qooxdoo hangs

On Wed, Oct 21, 2015 at 10:28 AM, Kenneth Tilton wrote: > > > On Tue, Oct 20, 2015 at 12:16 PM, Kenneth Tilton > wrote: > >> Never mind. It finally occurred to me to try FireFox, and that still >> hangs but manages to output the last console logging and indeed I see the >> expected messages. Now

Re: [qooxdoo-devel] qx.io.remote.Request queued but not queued and qooxdoo hangs

On Tue, Oct 20, 2015 at 12:16 PM, Kenneth Tilton wrote: > Never mind. It finally occurred to me to try FireFox, and that still hangs > but manages to output the last console logging and indeed I see the > expected messages. Now exploring much further downstream. :) > No, I was right the first ti

Re: [qooxdoo-devel] qx.io.remote.Request queued but not queued and qooxdoo hangs

Never mind. It finally occurred to me to try FireFox, and that still hangs but manages to output the last console logging and indeed I see the expected messages. Now exploring much further downstream. :) -kt On Tue, Oct 20, 2015 at 9:55 AM, Kenneth Tilton wrote: > Stack: > >1. Windows 7, se

[qooxdoo-devel] qx.io.remote.Request queued but not queued and qooxdoo hangs

Stack: 1. Windows 7, server and client, client talking to server as localhost 2. qooxdoo dsktop 5.0.1 just now downloaded 3. Chrome browser just updated 4. AllegroServe (Lisp) server Problem synopsis: remote table load request (and everything else) works for 98% of (it so happens) stu

Re: [qooxdoo-devel] qx.io.remote.Request[51-1]: Received id (undefined) does not match requested id

On Fri Jan 23 2015 at 3:56:43 AM halcwb wrote: > You're completely right about the 'id' requirement. Unfortunately, there is > no easy way to fix this in the qooxdoo framework. I tried to follow you're > suggestion, only the response event doesn't contain a response object, but > a > response jso

Re: [qooxdoo-devel] qx.io.remote.Request[51-1]: Received id (undefined) does not match requested id

Derrell Lipman wrote > Got it. The ExtJs server apparently implements something that claims to be > JSON-RPC, but doesn't follow the JSON-RPC protocol. (The field "id" is not > allowed to be called "tid" in a JSON-RPC request or response.) > > So, you have a couple of choices. The easy one for me

Re: [qooxdoo-devel] qx.io.remote.Request[51-1]: Received id (undefined) does not match requested id

On Wed Jan 21 2015 at 9:37:16 AM halcwb wrote: > So, there is an *id* field, only the field is called *tid*. This is because > the service was meant to work with ExtJs, and for that framework, the reply > should be identified by a 'tid' instead of an id (probably the t is for > transaction). I do

Re: [qooxdoo-devel] qx.io.remote.Request[51-1]: Received id (undefined) does not match requested id

Derrell Lipman wrote > This sounds like your service implementation isn't really implementing > JSON-RPC, or I'm not understanding your issue. JSON-RPC *requires* that > there be an *id* field (or that it be missing, in which case it's a > "notification"). It can't be any other name. Here's the JSO

Re: [qooxdoo-devel] qx.io.remote.Request[51-1]: Received id (undefined) does not match requested id

This sounds like your service implementation isn't really implementing JSON-RPC, or I'm not understanding your issue. JSON-RPC *requires* that there be an *id* field (or that it be missing, in which case it's a "notification"). It can't be any other name. Here's the JSON-RPC spec, with which the qo

[qooxdoo-devel] qx.io.remote.Request[51-1]: Received id (undefined) does not match requested id

I have this override f the qx.io.remote.Request: [CODE] qx.Class.define "informedica.io.remote.Rpc", extend: qx.io.remote.Rpc statics: _URL: '../../../DirectRouter/Index' _rpc: -> new informedica.io.remote.Rpc() ### Perform an RPC with @param service {String}: the servi

Re: [qooxdoo-devel] qx.io.remote.Request and database record locking

rs I have a modified version. MySQL will handle the simultaneous writing automatically. Matt -Original Message- From: Raymond Rösch [mailto:r.roe...@roeschinformatik.ch] Sent: Thursday, March 15, 2012 3:48 PM To: qooxdoo-devel Subject: [qooxdoo-devel] qx.io.remote.Request and database rec

[qooxdoo-devel] qx.io.remote.Request and database record locking

Dear qooxdoo community I am developping qooxdoo applications using remote requests to read and write data by php from or to a mysql database. I would like to lock database records on a row basis prior to update. The idea is to prevent from data loss when two persons update the same record at the

Re: [qooxdoo-devel] qx.io.remote.Request

Thanks Gabi, that must be the solution, I call getLogged() too early ;) Tero On Fri, Apr 15, 2011 at 12:48 PM, Gabriel Munteanu < gabriel.munte...@1and1.ro> wrote: > Maybe you call myInstanceOfelaskut.ElaskuService.getLogged() right after > myInstanceOfelaskut.ElaskuService.login() ? > mind you

Re: [qooxdoo-devel] qx.io.remote.Request

Maybe you call myInstanceOfelaskut.ElaskuService.getLogged() right after myInstanceOfelaskut.ElaskuService.login() ? mind you that you should wait for the "completed" event before you call getLogged. i could help you more if i see how you call getLogged(). cheers, Gabi -- View this message in co

Re: [qooxdoo-devel] qx.io.remote.Request

Thanks for Your fast replies, there is obviously something that I don't quit understand, my code below and it does not work: qx.Class.define("elaskut.ElaskuService", { extend : qx.core.Object, members : { logged : "", getLogged: function() { return this.logged }, login :

Re: [qooxdoo-devel] qx.io.remote.Request

you're right, Jim, "this" referred to the req, that was the reason for his problem most sure. -- View this message in context: http://qooxdoo.678.n2.nabble.com/qx-io-remote-Request-tp6275429p6275647.html Sent from the qooxdoo mailing list archive at Nabble.com. --

Re: [qooxdoo-devel] qx.io.remote.Request

Not quite correct. In the code segment presented, the 'this' referred to the req object and nothing else. So this.data is only associated with the req object. He needs to provide the correct scope to the method in order to get clarity. Jim On Fri, Apr 15, 2011 at 1:28 AM, Gabriel Munteanu wrote

Re: [qooxdoo-devel] qx.io.remote.Request

Hi, is data a public member of the class? If so, it should work, but i cannot say from your example, as I don't see how data is defined and the way you access it from your other class. A nice way would be to add getter and setter to that member, or make it a property and you have getter and setter

Re: [qooxdoo-devel] qx.io.remote.Request

What is happening is that you are getting your scope confused. If I read your code I have no idea what your intent is for this.data. Are you intending the data to be a property of the req? Well, it is. What you probably want is for the data to be associated with another object. To do that, you need

Re: [qooxdoo-devel] qx.io.remote.Request

Hi Tero, When you say "class member" do you mean a property or something that is in the members:{ } collection? Cheers, - Andrew - Andrew Manson Graticule Cloud Applications www.graticule.com On 15 Apri

[qooxdoo-devel] qx.io.remote.Request

Hi, When request is completed how can I put content to a class member? for example, this.data = e.getContent(); seems to work but when I access it form another class data is not set. var req = new qx.io.remote.Request("http://localhost:8080/jlogin/";, "GET", "application/json"); req.addListener

Re: [qooxdoo-devel] qx.io.remote.Request error

On Tue, Mar 22, 2011 at 07:33, Jagget wrote: > In this example code I receive only bug in Firebug console: > > var req = new qx.io.remote.Request("http://www.jagget.org/p/blog-page.html";, > "GET", "text/html"); > req.setCrossDomain(true); > req.addListener("completed", function(e) { > alert(

[qooxdoo-devel] qx.io.remote.Request error

In this example code I receive only bug in Firebug console: var req = new qx.io.remote.Request("http://www.jagget.org/p/blog-page.html";, "GET", "text/html"); req.setCrossDomain(true); req.addListener("completed", function(e) { alert(e.getContent()); }); req.send(); 003322 qx.io.remote.Exchan

Re: [qooxdoo-devel] qx.io.remote.Request not being sent from IE

Jim Hunter wrote: > I use relative URL's exclusively and with no problems in any browser. > A 'site' can't have multiple domain names, that would make them > multiple sites and you would need to follow all of the cross site > scripting rules to make calls between them with one of the > requiremen

Re: [qooxdoo-devel] qx.io.remote.Request not being sent from IE

I use relative URL's exclusively and with no problems in any browser. A 'site' can't have multiple domain names, that would make them multiple sites and you would need to follow all of the cross site scripting rules to make calls between them with one of the requirements being that you have to use

Re: [qooxdoo-devel] qx.io.remote.Request not being sent from IE

Rod K wrote: > thron7 wrote: > Hum, this is indeed strange. Only thing that comes to my mind quickly is add "alert()" to the method, e.g. "alert(url)" just before creating req, and try the constructed url in a separate browser window by hand, see what happens. Maybe IE need

Re: [qooxdoo-devel] qx.io.remote.Request not being sent from IE

thron7 wrote: >>> Hum, this is indeed strange. Only thing that comes to my mind quickly is >>> add "alert()" to the method, e.g. "alert(url)" just before creating req, >>> and try the constructed url in a separate browser window by hand, see >>> what happens. Maybe IE needs a server part at the u

Re: [qooxdoo-devel] qx.io.remote.Request not being sent from IE

Joe Noon wrote: >> _loadRowCount: function () >>{ >>var url = "/dns_zone_count.php"; >>var req = new qx.io.remote.Request(url, "GET", >> "application/json"); >>req.addListener("completed", this._onRowCountCompleted, this); >>alert(url); >>

Re: [qooxdoo-devel] qx.io.remote.Request not being sent from IE

Does this solve your issue? Otherwise, could you please add a listener to "changeState" and log the state changes. What is you last state? Cheers, Chris Am 18.03.2010 10:36, schrieb Joe Noon: >> _loadRowCount: function () >> { >> var url = "/dns_zone_count.php"; >>

Re: [qooxdoo-devel] qx.io.remote.Request not being sent from IE

> _loadRowCount: function () >        { >            var url = "/dns_zone_count.php"; >            var req = new qx.io.remote.Request(url, "GET", > "application/json"); >            req.addListener("completed", this._onRowCountCompleted, this); >            alert(url); >            req.send(); >  

Re: [qooxdoo-devel] qx.io.remote.Request not being sent from IE

>> Hum, this is indeed strange. Only thing that comes to my mind quickly is >> add "alert()" to the method, e.g. "alert(url)" just before creating req, >> and try the constructed url in a separate browser window by hand, see >> what happens. Maybe IE needs a server part at the url? (Actually, I >>

Re: [qooxdoo-devel] qx.io.remote.Request not being sent from IE

thron7 wrote: > On 03/17/2010 05:43 PM, Rod K wrote: > >> New qooxdoo user. I've searched and not found anything related. >> >> Using 1.0.1 and making a non-cross-domain request. Everything works >> fine in FF 3.6, Opera, Safari and Chrome, but not in any version of IE >> tested (6, 7 & 8).

Re: [qooxdoo-devel] qx.io.remote.Request not being sent from IE

On 03/17/2010 05:43 PM, Rod K wrote: > New qooxdoo user. I've searched and not found anything related. > > Using 1.0.1 and making a non-cross-domain request. Everything works > fine in FF 3.6, Opera, Safari and Chrome, but not in any version of IE > tested (6, 7 & 8). > > No request is sent t

[qooxdoo-devel] qx.io.remote.Request not being sent from IE

New qooxdoo user. I've searched and not found anything related. Using 1.0.1 and making a non-cross-domain request. Everything works fine in FF 3.6, Opera, Safari and Chrome, but not in any version of IE tested (6, 7 & 8). No request is sent to the server from IE and no errors are being reported

Re: [qooxdoo-devel] qx.io.remote.request with 'username' with parameter, request won't send?

I captrued every request in firefox. And server didn't receive any request. Sonothing was sent On 6/6/09, Gene Amtower wrote: > On Sat, 2009-06-06 at 10:17 +0800, ma ming wrote: > >> Dear all, I'm new to qooxdoo, and I found that when I trying to send a >> request with 'username' as a paramet

Re: [qooxdoo-devel] qx.io.remote.request with 'username' with parameter, request won't send?

On Sat, 2009-06-06 at 10:17 +0800, ma ming wrote: > Dear all, I'm new to qooxdoo, and I found that when I trying to send a > request with 'username' as a parameter. > The request won't be sent out. > > var loginRequest = new qx.io.remote.Request > ('/user/userlogin/',"POST","text/plain");

Re: [qooxdoo-devel] qx.io.remote.request with 'username' with parameter, request won't send?

loginRequest.setParameter(..,..) will cause the same result. And I don't know the exactly different between these two functions. I checked the Iframe.js but I didn't see any code relate to 'username'. On Sat, Jun 6, 2009 at 3:48 PM, Derrell Lipman < derrell.lip...@unwireduniverse.com> wrote: > On

Re: [qooxdoo-devel] qx.io.remote.request with 'username' with parameter, request won't send?

On Fri, Jun 5, 2009 at 10:17 PM, ma ming wrote: > Dear all, I'm new to qooxdoo, and I found that when I trying to send a > request with 'username' as a parameter.The request won't be sent out. > > var loginRequest = new > qx.io.remote.Request('/user/userlogin/',"POST","text/plain"); >

[qooxdoo-devel] qx.io.remote.request with 'username' with parameter, request won't send?

Dear all, I'm new to qooxdoo, and I found that when I trying to send a request with 'username' as a parameter.The request won't be sent out. var loginRequest = new qx.io.remote.Request('/user/userlogin/',"POST","text/plain"); loginRequest.setFormField("password","mamamama");

Re: [qooxdoo-devel] qx.io.remote.Request Multiple sending

mapp...@libero.it wrote: > Hi, > > I need to send the same request more times (eg. if a session timeout the > user has to login, but I will senda again the previous request without user > action). > If I send more then one time the same request object every listener > and parameter is lost. >

[qooxdoo-devel] qx.io.remote.Request Multiple sending

Hi, I need to send the same request more times (eg. if a session timeout the user has to login, but I will senda again the previous request without user action). If I send more then one time the same request object every listener and parameter is lost. Is it possible to use the same listeners a

Re: [qooxdoo-devel] qx.io.remote.Request not working anymore with POST ?

Thanks for your quick answer :-) ! Derrell Lipman wrote: > > On Tue, Feb 17, 2009 at 3:04 PM, benco wrote: > >> >> Strange behaviour with the current svn qooxdoo version, this kind of code >> always send a GET request ... >> >> // httpPath = user variable >> var req = new >> qx.io.remote.Req

Re: [qooxdoo-devel] qx.io.remote.Request not working anymore with POST ?

On Tue, Feb 17, 2009 at 3:04 PM, benco wrote: > > Strange behaviour with the current svn qooxdoo version, this kind of code > always send a GET request ... > > // httpPath = user variable > var req = new > qx.io.remote.Request("http:// > "+httpPath+"/path/script.php","POST","text/plain"); > req.s

[qooxdoo-devel] qx.io.remote.Request not working anymore with POST ?

Hi, Strange behaviour with the current svn qooxdoo version, this kind of code always send a GET request ... // httpPath = user variable var req = new qx.io.remote.Request("http://"+httpPath+"/path/script.php","POST","text/plain";); req.setTimeout(15000); req.setCrossDomain(true);

Re: [qooxdoo-devel] qx.io.remote.Request

> It seems I can't even do POST requests INSIDE my domain: If I do > setCrossDomain(false) and try to get data from another machine that > doesn't > work either. (Machine 1: 192.168.1.10 - Machine 2: 192.168.1.11) > So that seems to be even more restrictive, because it seems to look for > change

Re: [qooxdoo-devel] qx.io.remote.Request

On Fri, Feb 6, 2009 at 12:23 PM, Andy Fuchs wrote: > On 06.02.09 17:41, "Derrell Lipman" > wrote: > > > You've discovered the "same domain" requirement imposed by the browsers > for > > security reasons. > > > > qooxdoo provides three transports for remote requests (XmlHTTP, IFrame, > and > > Sc

Re: [qooxdoo-devel] qx.io.remote.Request

On 06.02.09 17:41, "Derrell Lipman" wrote: > You've discovered the "same domain" requirement imposed by the browsers for > security reasons. > > qooxdoo provides three transports for remote requests (XmlHTTP, IFrame, and > Script), and selects from among the transports based on the requirements

Re: [qooxdoo-devel] qx.io.remote.Request

On Fri, Feb 6, 2009 at 11:19 AM, Andy Fuchs wrote: > > 1.) It seems I can't use 'POST' when trying to get data across domains > (rpc.setCrossDomain(true)). Is this a bug or is this SOP? Is there any > other way in Qooxdoo to get data across domains using POST? (It seems that > doesn't even work

Re: [qooxdoo-devel] qx.io.remote.Request

Sorry for the long post, but I need some help and wanted to give as much information as possible: 1.) It seems I can't use 'POST' when trying to get data across domains (rpc.setCrossDomain(true)). Is this a bug or is this SOP? Is there any other way in Qooxdoo to get data across domains using POS

Re: [qooxdoo-devel] qx.io.remote.Request

I had to leave "application/json" for "text/plain". That's the only way I found (in the incredible hurry I am, so maybe there is other solutions) to ensure POST request using json string in it. The only thing is that I have to do that by hand aftet the request succedd : var req = new qx.io.r

Re: [qooxdoo-devel] qx.io.remote.Request

Hi Florian, I already tried that too, with no success. If I do a TCPDump of the request, it turns out, that the Transport-method changes from 'POST' to 'GET' no matter what I specify... That's why communication fails... What can I do to ensure 'POST'?? thx andy On 06.02.09 13:33, "Florian

Re: [qooxdoo-devel] qx.io.remote.Request

Hello Andy, if you want to execute jscon rpcs then you should use http://demo.qooxdoo.org/current/apiviewer/index.html#qx.io.remote.Rpc. It works perfect and is much more comfortable. You can even choose between diffrent backend implementations (PHP, Perl, ...) if you need one. Regards, Florian

[qooxdoo-devel] qx.io.remote.Request

Hi folks, I am struggling with a very basic problem: I try to get data from a server, but all I get is a parameter error. Communication is json-rpc Transport-method is 'POST'. The native call is curl -d "{ \"method\": \"test.anymethod\", \"id\": 1 }" http://192.168.1.1/myControl and works fin

Re: [qooxdoo-devel] qx.io.remote.Request

I have found source of problem, I'm good, but I thing that this is problem in qooxdoo. If there is exception in the "completed" handler, qooxdoo will timeout it. I thing that if this is "normal" behavior, it should be written in documentation. Helder, thanx for some info. I'm posted this problem

Re: [qooxdoo-devel] qx.io.remote.Request

petr kobalicek-2 wrote: > > I'm not sending code, because it's very simple, just create request, > addParameter(), set callbacks and send(). > It is _always_ a good idea sending a reduced test case whenever possible! :-p A cool (and easy) way to do it is creating a demo browser sample [1]. ;-)

[qooxdoo-devel] qx.io.remote.Request

Hi, I'm getting always timeout when I'm using GET requests (qx.io.remote.Request) This is from firebug: GET http://localhost:5000/browser/list/?path=%2F (124ms)qx_gecko.js (line 141)ParamsHeadersPostResponseCache Response Headers Request Headers {"result": {"files": [], "dirs": ["..", "admin"

Re: [qooxdoo-devel] qx.io.remote.Request can't send more than one times

jhonny, unfortunately, qx.io.remote.Request objects are "single-use-only" (see http://demo.qooxdoo.org/current/apiviewer/#qx.io.remote). put the "var req = new ..." and "req.addEventListener(..." statements inside the b1 event listener, and it should work. thomas > Hi... > I use remote reques

[qooxdoo-devel] qx.io.remote.Request can't send more than one times

Hi... I use remote request to communicate with PHP from qooxdoo. Here is my code : var d = qx.ui.core.ClientDocument.getInstance(); lyrketik = new qx.ui.form.TextArea(); lyrketik.set({ left: 1, top: 25, right: 1, bottom: 1 }); d.add(lyrketik); var b1 = ne

Re: [qooxdoo-devel] qx.io.remote.Request How to handle with SOAP XML Using Method "POST"

hello i don't know if u found the answer, but i might have a tip: Parameters are currently always sent using GET. Even if you select POST. This issue is already known and will be fixed with an enhanced data handling for our transport API in the future. from this page: http://qooxdoo.org/docum

Re: [qooxdoo-devel] qx.io.remote.Request How to handle with SOAP XML Using Method "POST"

Hello, thank you for your answer... I add my response down there. Nicolai Slaby wrote: > > qx.io.remote.Request("http://servername/ip_detect/services/Adminservice","PO ST","application/xml"); > Are you making the request from the same server/port ("servername")? Remote request are, due to secur

Re: [qooxdoo-devel] qx.io.remote.Request How to handle with SOAP XML Using Method "POST"

Nicolai Slaby wrote: > > qx.io.remote.Request("http://servername/ip_detect/services/Adminservice","POST","application/xml";); > Are you making the request from the same server/port ("servername")? Remote request are, due to security constraints, usually limited to requests made to the same ser

[qooxdoo-devel] qx.io.remote.Request How to handle with SOAP XML Using Method "POST"

Hello, i just started a few days ago with qooxdoo (0.7.2) and i really enjoy to work with this framework, but now i get stuck in some problem. (Maybe my question is stupid i don´t know) I try to make an request using method “POST” to an AXIS2 based Webservice (SOAP). I use an XML for posting i

Re: [qooxdoo-devel] qx.io.remote.Request doesn't work in synchronous mode properly in 0.7 Qx.

Fabian Jakobs schrieb: > Derrell Lipman schrieb: > >> On 7/5/07, Sergei Kolomiets <[EMAIL PROTECTED]> wrote: >> >> >>> Hi! >>> >>> After migrating from 0.6.6 version to 0.7 I found, that synchronous requests >>> don't work in IE 6. >>> Code line, placed after req.send() executes before t

Re: [qooxdoo-devel] qx.io.remote.Request doesn't work in synchronous mode properly in 0.7 Qx.

Derrell Lipman wrote: > >> Hi, Derrell. >> Sad to say, there are a lot of problems which can be solved via sync >> calls >> very easy. >> And they become too complex via async calls. >> For example, dynamic loading qx class before creating instance (sorry if >> I >> bring up old topics). >> Bes

Re: [qooxdoo-devel] qx.io.remote.Request doesn't work in synchronous mode properly in 0.7 Qx.

> Hi, Derrell. > Sad to say, there are a lot of problems which can be solved via sync calls > very easy. > And they become too complex via async calls. > For example, dynamic loading qx class before creating instance (sorry if I > bring up old topics). > Besides the native AcitveX sync request work

Re: [qooxdoo-devel] qx.io.remote.Request doesn't work in synchronous mode properly in 0.7 Qx.

Derrell Lipman wrote: > > On 7/5/07, Fabian Jakobs <[EMAIL PROTECTED]> wrote: >> Derrell Lipman schrieb: >> > On 7/5/07, Sergei Kolomiets <[EMAIL PROTECTED]> wrote: >> > >> >> Hi! >> >> >> >> After migrating from 0.6.6 version to 0.7 I found, that synchronous >> requests >> >> don't work in IE 6

Re: [qooxdoo-devel] qx.io.remote.Request doesn't work in synchronous mode properly in 0.7 Qx.

On 7/5/07, Fabian Jakobs <[EMAIL PROTECTED]> wrote: > Derrell Lipman schrieb: > > On 7/5/07, Sergei Kolomiets <[EMAIL PROTECTED]> wrote: > > > >> Hi! > >> > >> After migrating from 0.6.6 version to 0.7 I found, that synchronous > >> requests > >> don't work in IE 6. > >> Code line, placed after re

Re: [qooxdoo-devel] qx.io.remote.Request doesn't work in synchronous mode properly in 0.7 Qx.

Derrell Lipman schrieb: > On 7/5/07, Sergei Kolomiets <[EMAIL PROTECTED]> wrote: > >> Hi! >> >> After migrating from 0.6.6 version to 0.7 I found, that synchronous requests >> don't work in IE 6. >> Code line, placed after req.send() executes before than event handler >> "completed" executed. >>

Re: [qooxdoo-devel] qx.io.remote.Request doesn't work in synchronous mode properly in 0.7 Qx.

Derrell Lipman wrote: > > On 7/5/07, Sergei Kolomiets <[EMAIL PROTECTED]> wrote: >> >> Hi! >> >> After migrating from 0.6.6 version to 0.7 I found, that synchronous >> requests >> don't work in IE 6. >> Code line, placed after req.send() executes before than event handler >> "completed" executed

Re: [qooxdoo-devel] qx.io.remote.Request doesn't work in synchronous mode properly in 0.7 Qx.

On 7/5/07, Sergei Kolomiets <[EMAIL PROTECTED]> wrote: > > Hi! > > After migrating from 0.6.6 version to 0.7 I found, that synchronous requests > don't work in IE 6. > Code line, placed after req.send() executes before than event handler > "completed" executed. > > How I need to execute synchronous

[qooxdoo-devel] qx.io.remote.Request doesn't work in synchronous mode properly in 0.7 Qx.

Hi! After migrating from 0.6.6 version to 0.7 I found, that synchronous requests don't work in IE 6. Code line, placed after req.send() executes before than event handler "completed" executed. How I need to execute synchronous requests? Thanks -- View this message in context: http://www.nabbl

[qooxdoo-devel] qx.io.remote.Request Post-Params

Hello, how can I send Values via Post-Method to the server? r.setParameter("test","abc") is for "get"-Values, isn't it? Thanks a lot Tobias - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.ne

Re: [qooxdoo-devel] qx.io.remote.Request

> [EMAIL PROTECTED] writes: > > Yes. I know this, but status code is not enough for me. The text > > information given in the body (even in case of status codes: 500, 404 > > etc.) is very useful for me (it includes the error message to be shown to > > user) > > What about e.getData().getResponseHe

Re: [qooxdoo-devel] qx.io.remote.Request

[EMAIL PROTECTED] writes: > Yes. I know this, but status code is not enough for me. The text information > given in the body (even in case of status codes: 500, 404 etc.) is very > useful for me (it includes the error message to be shown to user) What about e.getData().getResponseHeaders()? Do

Re: [qooxdoo-devel] qx.io.remote.Request

Yes. I know this, but status code is not enough for me. The text information given in the body (even in case of status codes: 500, 404 etc.) is very useful for me (it includes the error message to be shown to user) > [EMAIL PROTECTED] writes: > > I noticed that when the Request is "failed" ther

Re: [qooxdoo-devel] qx.io.remote.Request

[EMAIL PROTECTED] writes: > I noticed that when the Request is "failed" there are no data in > e.getData().getContent() (in "failed" handler)? I'm sure that content > exists there (at least, Firebug shows me), but qooxdoo doesn't ... I think what you want is e.getData().getStatusCode() which prov

Re: [qooxdoo-devel] qx.io.remote.Request

Hi List, hi Sebastian Sorry for not responding for a long-time. I was ill and did't have access to the internet. > > I noticed that when the Request is "failed" there are no data in > > e.getData().getContent() (in "failed" handler)? I'm sure that content > > exists there (at least, Firebug show

Re: [qooxdoo-devel] qx.io.remote.Request parameters vs form fields and GET vs POST

Hi Derrell, Am 31.01.2007 um 15:09 schrieb [EMAIL PROTECTED]: >> I think we could easily check for invalid combinations. As soon as >> a user >> adds parameters to the body (via the proposed addBodyParameter >> method), we >> can throw an exception in case he sets the content type to >> any

Re: [qooxdoo-devel] qx.io.remote.Request parameters vs form fields and GET vs POST

Andreas Junghans <[EMAIL PROTECTED]> writes: > I think we could easily check for invalid combinations. As soon as a user > adds parameters to the body (via the proposed addBodyParameter method), we > can throw an exception in case he sets the content type to anything else > than application/x-www

Re: [qooxdoo-devel] qx.io.remote.Request parameters vs form fields and GET vs P

> I've checked RFC2616, the HTTP 1.1 spec. I don't see anything that > prohibits > query parameters on a POST. The current implementation, sending query > parameters if any are provided, appears legal and reasonable. Agreed, as section 3.2 defines the URI independent on the method. It would ap

Re: [qooxdoo-devel] qx.io.remote.Request parameters vs form fields and GET vs POST

Hi Derrell, Am 30.01.2007 um 22:07 schrieb [EMAIL PROTECTED]: > Andreas Junghans <[EMAIL PROTECTED]> writes: > >>> Ultimately, it would be nice to have a generic "form" API that >>> allows >>> generating forms using qooxdoo widgets and having the submission >>> of the >>> form data be automat

Re: [qooxdoo-devel] qx.io.remote.Request parameters vs form fields and GET vs POST

Andreas Junghans <[EMAIL PROTECTED]> writes: >> Ultimately, it would be nice to have a generic "form" API that allows >> generating forms using qooxdoo widgets and having the submission of the >> form data be automated (or at least semi-automated). That's a bit more of >> a project than is requir

Re: [qooxdoo-devel] qx.io.remote.Request parameters vs form fields and GET vs POST

[EMAIL PROTECTED] writes: > Ok, that's fine. IIRC, someone posted a reference yesterday that indicated > that sending parameters on a POST was a violation off the spec. (Am I > remembering that correctly?) If that's so, then I believe that the default > behavior should be to conform to the spec

Re: [qooxdoo-devel] qx.io.remote.Request parameters vs form fields and GET vs POST

Hi Derrell, Am 30.01.2007 um 19:03 schrieb [EMAIL PROTECTED]: >> Removed two limiting if clauses, because attaching Parameters to >> the URL >> used to be perfectly ok, even for POST requests. Unfortunately, >> your changes >> would have broken existing apps that already use such a supported

[qooxdoo-devel] qx.io.remote.Request parameters vs form fields and GET vs POST

Moving this discussion to qooxdoo-devel... Andreas Ecker <[EMAIL PROTECTED]> writes: > * My only changes to your check-in: Sorry, I did misunderstand the scope of the changes you were making. It looked much larger than it was. > Removed two limiting if clauses, because attaching Parameters to

Re: [qooxdoo-devel] qx.io.remote.Request changes

> I have added (in svn) a new feature to remote requests, to allow > programatically providing form field data to be added to a request. See my response to your previous posting about header parameters. Also, I don't understand why you have to switch to IFrame... Hugh --

[qooxdoo-devel] qx.io.remote.Request changes

I have added (in svn) a new feature to remote requests, to allow programatically providing form field data to be added to a request. Previously, various people had asked that "parameters" that they specified with request.setParameter() be passed as form fields in IframeTransport. That turns out to

Re: [qooxdoo-devel] qx.io.remote.Request

[EMAIL PROTECTED] schrieb: > Hello, > > I noticed that when the Request is "failed" there are no data in > e.getData().getContent() (in "failed" handler)? I'm sure that content exists > there (at least, Firebug shows me), but qooxdoo doesn't ... What do you mean exactly with "data" in this case

[qooxdoo-devel] qx.io.remote.Request

Hello, I noticed that when the Request is "failed" there are no data in e.getData().getContent() (in "failed" handler)? I'm sure that content exists there (at least, Firebug shows me), but qooxdoo doesn't ... Is that a bug or feature? Thanks, Alexei Golovko --

Re: [qooxdoo-devel] qx.io.remote.Request does not work in Firefox 2.0.0.1

> As additional information: a response to the firefox POST request is > "411 > Length Required". > Is it possible to set a content length to the POST request? I'm not really the right person to ask, but it works for us. Checking in the server (we have our own written in Python) I can see that

Re: [qooxdoo-devel] qx.io.remote.Request does not work in Firefox 2.0.0.1

Michail Zabolotko wrote: > > > This problem appeared before installing firebug. Anyway, I'll keep this in > mind. > Attractive fact: GET is work fine in Firefox. "failed" event is caused by > POST request. > > var req = new qx.io.remote.Request(Common.Io.Urls.inc, "GET", > "text/plain"); - w

Re: [qooxdoo-devel] qx.io.remote.Request does not work in Firefox 2.0.0.1

Hugh Gibson wrote: > > Actually, there was a bug in Firebug which caused it to swallow some > remote requests. You might be running into that problem. Try disabling it > if you have it installed. > > Hugh > > This problem appeared before installing firebug. Anyway, I'll keep this in mind. A

Re: [qooxdoo-devel] qx.io.remote.Request does not work in Firefox 2.0.0.1

> Are you using FireBug (www.getfirebug.com)? If not, > install it and it should point you to the reason there is an issue. > It has a request/response debugger so you can see all requests going > to the server. This should help. Actually, there was a bug in Firebug which caused it to swallow so

Re: [qooxdoo-devel] qx.io.remote.Request does not work in Firefox 2.0.0.1

Hard to say. I do this sort of thing all the time and it works fine on all versions of FF do date. Are you using FireBug (www.getfirebug.com)? If not, install it and it should point you to the reason there is an issue. It has a request/response debugger so you can see all requests going to the ser

[qooxdoo-devel] qx.io.remote.Request does not work in Firefox 2.0.0.1

Hi all! I have a problem with transport api of qooxdoo. I use qx.io.remote.Request as follows var req = new qx.io.remote.Request( Common.Io.Urls.inc , qx.net.Http.METHOD_POST , "text/plain" );

  1   2   >