Hi Alex, this happened exactly when backend (PHP) returned "Services require JSON-RPC" (dunno why this happened when normaly this doesn't happen :), but now it seems to be OK again ... I'll start new thread for another problem.
Thanks for help, Martin > Hi Martin, > > Martin wrote: > > To thank you, may be I have some improvement for rpc.js :) >> >> in this code: when response is null (when the reply is not XML data, >> i.e. >> some server error or bad call, it happened to me when I was restarting >> webserver). Then id = response["id"] raises error, because response is >> null, so may be code: > I'm wondering why you're running into this problem. Normally the > response has a value if the "completed" event is fired and the listener > is called. > In cases of a server error or a bad call the "failed" listener should be > called. And if you're request is fine but returns no data, then probably > the server backend has to be fixed. > So there should be no need to check the response object against "null", > I guess. > > Just my 2cents, > Alex ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
