I used Ajax to handle a large search results page for editing of the returned records and found it easy to use, very realible, cross browser, and stable. So I say bunk to all this....I think its the particular coder. Put your noggin to work bonehead, and engineer another solution if you are having trouble with the first. I find it so reliable that I can edit three records before the page finishes loading (large record reurns)...reliably...and to boot...there are 5000 users hitting my site, so you can't argue its a fluke.
The reason there is so much of a buzz about Ajax is because when combined with DHTML you can handle many fundamentals on the UI wishlist, like not having to reload the page for every little thing. Does that mean Ajax is the proper solution for all problems? obviously not. Use a proper systems approach and use Ajax where it is appropriate, however and you will be a better web developer for it.
This is a good way to go. A friend of mine outsourced in this way initially and has managed to come across a team of developers in India who are loyal and willing to work with him on new terms. They work from a UML methodology and are willing to use any preferred platform. This relationship has even evolved into one where the development team is willing to develop for him up front, and accept pay on speculated profits as a percentage until a slightly inflated pay off is reached. Yeah, its kind of like a no risk unlimited trial on the code with no interest and no payments until it pays for itself. Just remember that they are people over there also, and are willing to build business relationships just as we do over here.
Slashdot Mirror
thanks
enough said.
I used Ajax to handle a large search results page for editing of the returned records and found it easy to use, very realible, cross browser, and stable. So I say bunk to all this....I think its the particular coder. Put your noggin to work bonehead, and engineer another solution if you are having trouble with the first. I find it so reliable that I can edit three records before the page finishes loading (large record reurns)...reliably...and to boot...there are 5000 users hitting my site, so you can't argue its a fluke. The reason there is so much of a buzz about Ajax is because when combined with DHTML you can handle many fundamentals on the UI wishlist, like not having to reload the page for every little thing. Does that mean Ajax is the proper solution for all problems? obviously not. Use a proper systems approach and use Ajax where it is appropriate, however and you will be a better web developer for it.
This is a good way to go. A friend of mine outsourced in this way initially and has managed to come across a team of developers in India who are loyal and willing to work with him on new terms. They work from a UML methodology and are willing to use any preferred platform. This relationship has even evolved into one where the development team is willing to develop for him up front, and accept pay on speculated profits as a percentage until a slightly inflated pay off is reached. Yeah, its kind of like a no risk unlimited trial on the code with no interest and no payments until it pays for itself. Just remember that they are people over there also, and are willing to build business relationships just as we do over here.