Andrew thanks for your answer, Im gonna check the info you sent me.

One question, theoretic one . If, both, the Cococa App and the WO app, are using the same servers, its worth to make a WS to interoperate between them?, I dunno if I have made myself clear; as far as I remember form school, was that WS are used mostly to interoperate different applications with different logic and back end, so if my apps are using the same back end, whatever I do in on server it will be reflected on the other app and vise-versa no?
So again my question, do I need to make such a layer with WS's ?

Thanks


Gustavo

On May 4, 2009, at 11:47 PM, Andrew Lindesay wrote:

Hello Gustavo;

Im getting nuts here. Im trying to figure out how to integrate a Cocoa app with a WO app,

I have an open-source WebObjects <---> Cocoa WS infrastructure using the JSON-RPC protocol...

        http://en.wikipedia.org/wiki/JSON-RPC

...which is already deployed into a production system and is working well. It sounds like it may be perfect for your purposes. It is documented here;

        
http://homepage.mac.com/andrewlindesay/le/manuals/lewostuff/LEWOStuffOverview.pdf
        (7.24 JSON-RPC)
        (8. liblecocoastuff)

Also see;

        http://www.wocommunity.org/wowodc08/sessions/json-rpc.html

There are JSON-RPC clients for numerous languages, but I supply open- source clients for;

        ActionScript-3
        JavaScript
        Java
        Cocoa

On a commercial-basis around this, I can;

        * enhance "LEWOStuffOverview.pdf" to answer questions
        * answer questions by email
        * provide code samples
        * provide proof-of-concepts
        * undertake development projects

cheers.

___
Andrew Lindesay
www.lindesay.co.nz


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to