On Sun, Oct 19, 2008 at 2:11 PM, Red Davies <[EMAIL PROTECTED]> wrote:
> Greetings!
Greetings!
>
> After couple of weeks of trawling through sources, examples and
> documentation I finally have given in and have to ask for help.
We're generally a friendly bunch; we typically don't bite. :-) Feel free to
ask questions after a reasonable amount of research on your own. There's no
reason to go weeks at a time without finding an answer or asking a question.
I think I'm having a fundamental misunderstanding as to how
> communication happens between the javascript client application and my
> server.
>
> I tried following the initial documented examples using the perl rpc
> server but it doesn't seem to be present in the 0.8 release that I can
> find. The only versions I seem to be able to find seem to be in 0.7.
In 0.8, they've moved to qooxdoo-contrib (see
http://qooxdoo.org/contrib/for details on retrieving it). All three
of the standard backends are
available there (RpcJava, RpcPerl, RpcPhp), and a working example of using
them is available too (RpcExample). There's no backend available on the
qooxdoo web site, which is why you don't see examples of using it in the
demobrowser. You can, however, install an appropriate backend on your own
web server and then use RpcExample to experiment with it.
>
> I
> sniffed the traffic between my browser and the demo website and
> instead of seeing straight JSON come over the wire, I saw javascript.
> Now I'm thoroughly confused.
I would be too. What is sent between the JSON-RPC client and server
(backend) is JSON... with one extension. Since JSON doesn't support native
Date types, we've extended the JSON protocol that we use to allow for
sending dates. The format looks like javascript (new Date(...)) so if you
saw that, it may have confused you.
>
>
> I would assume that my bright idea of simply building a server that
> would return JSON data was a fools errand.
Nope. That's exactly what the three standard backends do. And if you want
a Perl backend, there's likely no reason to write your own; you can simply
add the methods you want to allow your client to be able to call remotely.
> A simple kick in the right direction will be sufficient for me to
> climb my way to working code.
Hopefully the pointer to qooxdoo-contrib is all you needed. If you have
other questions, though, feel free to ask.
Cheers,
Derrell
php backend author
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
