How to Implement an AJAX Solution.

[Gaffar]

Hello.

My name is Gaffar. I am handling an module in a Project. This application interface is slow and inefficient. So Client told "implement an AJAX Solution which will increase speed and efficiency and user's experience".

So, My problem is what is AJAX Solution. How to implement that. what are the feataures. Please give with a sample solution.

Thanx in advance.

Regards
Gaffar.

 

[Guest]

A couple of links to get you started (AJAX.net works quite nicely). Don't
forget to read the pros and cons to make sure that AJAX is the right solution
to your problem:

http://en.wikipedia.org/wiki/AJAX
http://ajax.schwarz-interactive.de/csharpsample/default.aspx

HTH, Jakob.

 

[Helge Lenuweit]

AJAX stands for Asynchronous Javascript and XML, a way to avoid page
post-back and full reload on every interaction a user does in the
browser window. You'll get more information and implementations here:

http://ajax.schwarz-interactive.de/csharpsample/default.aspx
http://jason.diamond.name/weblog/2005/07/06/my-ajax-dot-net-library
http://west-wind.com/weblog/posts/2658.aspx

Regards, Helge

 

[Cor Ligthert [MVP]]

Gaffar,

Ajax a Greek mythological person very well known from the Illias as well as a famous Dutch football club.

In Internet is meant to sent only parts of the server and page needs over the line. (In my idea is ASPNET doing the same, however I am not sure of it and never checked it).

I agree completely what with Jacob wrote, probably will that not shorten your total throughput in a way that gives any benefit.

Don't forget that the webrowser is not reading from the line however from the cache on disk where mostly forever your complete page is in once it is asked (And the first time Ajax (not the mythological figure or the Club) can not help you.

I hope this helps,

Cor

 

[John Bailo]

Hello.

My name is Gaffar. I am handling an module in a Project.
This application interface is slow and inefficient. So Client told
"implement an AJAX Solution which will increase speed and efficiency and
user's experience".

If the interface is "slow and inefficient" it's probably because of poor
design, and switching architectures is not going to save you.

A c# client calling web services is going to give you far more choices
than an "ajax" javascript solution.

So, I think you should tell the client that he doesn't know what he's
talking about.