• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: JSON and WebObjects
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: JSON and WebObjects


  • Subject: Re: JSON and WebObjects
  • From: John Lennard <email@hidden>
  • Date: Thu, 12 Nov 2009 00:07:27 +1300

Hi,

I have been doing a fair bit of json-rpc the last few days. There are a few approaches i have been using in my apps

In one.. i am using the json rpc at a component level for auto completion, and for the starting of and tracking of long running server processes. These both use LEWOStuff.. and andrew's json-rpc stuff works very well.

In another application, the site is actually a php site, and i am pulling data out of the webobjects app and then building pages to display the data returned. As its PHP and totally brain dead i am returning raw rows and not worrying about EO's.. these raw rows translate almost directly into PHP's associative arrays. This is primarily read only access into the application, again i am using lewostuff on the woa side and some PHP library of suspect parentage.

The main reason for this approach was to allow for the other developers and designers to be able to work on the pages without having to deal with the WO which is a database of car parts. The only real draw backs are that it is php, and the possible cost of continual requests into the woa (I am likely to cache this in memory to lower this load). It is however a lot cleaner and more search engine friendly than using AJAX style calls and javascript in the pages.

The car parts database/woa also provides a JSON-RPC interface that is used for updating the database with a small pure java app that reads internal databases and xml files and uploads it in batches.. This JSON-RPC is far better than having to deal with XML data. It runs three or four times faster than the xml, and uses much less bandwith.

If you want some examples just sing out and i can provide you with code.


Cheers
John

On 11/11/2009, at 7:26 PM, Andrew Lindesay wrote:

> Hello Don;
>
> The framework will deal with EO serialisation for you.  Watch the WOWODC-2009 video on this subject and check out the sample code which was shown in the video;
>
> 	http://homepage.mac.com/andrewlindesay/le/downloads/JSONRPCHandsOn-SessionCode-1sep2009.zip
>
> I think John Lennard is doing some foo like this at the moment... John?
>
> cheers.
>
>> I am wanting to pass EO Objects back and forth to an AJAX web application.  We have a need where the entire front wend web application will be designed by graphics designers, no developers involved, then it will be turned over to the Developers to make sure all the bits are filled in.  (management's words not mine).  But the developers cannot modify the design.
>> The way I expected would be the easiest to implement would be to use JSON and AJAX, to receive objects to populate the interface.
>
> ___
> Andrew Lindesay
> www.lindesay.co.nz
>

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >JSON and WebObjects (From: Don Lindsay <email@hidden>)
 >Re: JSON and WebObjects (From: Andrew Lindesay <email@hidden>)
 >Re: JSON and WebObjects (From: Don Lindsay <email@hidden>)
 >Re: JSON and WebObjects (From: Andrew Lindesay <email@hidden>)

  • Prev by Date: Re: Installing WO 543 on Linux
  • Next by Date: UTF8 and ContentEncoding
  • Previous by thread: Re: JSON and WebObjects
  • Next by thread: Re: JSON and WebObjects
  • Index(es):
    • Date
    • Thread