Hi Nick,
I've amended the JSONRPC.pm to log to a file wherever it was printing to
STDERR, and am getting the following log information:

Session id: f9373329e104dd87a652d093832b9523
POST Content type is 'application/json'
JSON received:  


I see that it's receving POST rather than GET - is this the problem?
(And if so, any pointers on where to fix it?)

Thanks,

James


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nick
Glencross
Sent: 30 January 2007 17:39
To: qooxdoo Development
Subject: Re: [qooxdoo-devel] Perl RPC - problems running

Hi James!

On 30/01/07, James Lavery <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi All,
> I'm trying out the Perl backend, and am having problems...
>
> I can get the
>
> 'Your HTTP Client is not using the JSON-RPC protocol'
>
> error when I point a browser at my server script.
>

Yes, that's what's expected. Certain arguments need to be passed by the
request for it to be proper JSON-RPC, so that's why this message is
shown.

> However, when I try running the test:
>
> http://localhost/qx/0.6.5/qooxdoo-0.6.5-sdk/frontend/application/sampl
> e/source/html/test/RPC_1.html
>
> I get the following errors (in the right-hand pane of the test page):
>
> qx.core.Object
> 960302: JSON request: 
> {"service":"qooxdoo.test","method":"echo","id":2,"params":["Hello"],"s
> erver_data":null}
> 960537: JSON response: A bad JSON-RPC request was received 
> qx.io.remote.XmlHttpTransport[1046]
> 960537: Could not execute json: [A bad JSON-RPC request was received
>  ]: SyntaxError - Expected ')' (#-2146827282) 
> qx.io.remote.Request[1040]
> 960537: Received id (undefined) does not match requested id (2)!
> Any ideas on what might be wrong, and/or tips on how to get more debug
info?  I'm running IIS.

Now, that's a little more strange. I don't currently have access to IIS
to check this (although I could at the weekend if it gets to that), so
do you mind checking enabling the debug flag in  JSONRPC.pm?

Around line 30, could you can the line to read

   $Qooxdoo::JSONRPC::debug = 1;

Although I've used IIS, I confess to not knowing where the messages
printed to STDERR go. Are you able to hunt them down? If not, I can send
you an updated version which writes to a file instead (and perhaps does
a little bit more tracing).

At first glance, it looks like either the CGI module isn't setting the
request_method, or a GET request is being received, but without the and
_ScriptTransport_ and id_ScriptTransport_data data.

Nick

------------------------------------------------------------------------
-
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE
V
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to