No, JSON is the correct route. If you are using ajax to retrieve
json, then you can pull the json into a javascript object
immediately. If you are using PHP to generate pages, then you can
print out the JSON object as a string directly into javascript and
create javascript objects that way. jQuery has built in methods
to .getJSON that provides the basis of all my AJAX calls in the web
app I work on.
Another tip, standardize all the JSON responses into a format you
like, for example
{
'header': {
'type': String,
'message': String
},
'payload': {
'data': []
}
}
That way you can create one object that calls .getJSON and use that
object to do all of your ajax calls and have a standard set of
responses to being timed out, 404 errors, loading alert while the ajax
call is running, etc.
Good luck.
On Mar 14, 7:38 am, dani <dan...@lapidus.se> wrote:
> Before taking on a challenging task, please give me some ideas to
> speed up my development!
>
> Just as the topic is saying, I will primarily be doing: MySQL => PHP
> => JSON => AJAX => jQueryUI
>
> I used to work with CakePHP but I have little experience with JSON.
> Any hints on your favourite tools and helpers (MVC frameworks, MySQL
> tools, JSON parsers, jQuery extensions etc.) are greatly appreciated.
>
> If you think I should modify my "route", for example XML instead of
> JSON, please put forward the pros and cons.
>
> Thanks.
