asp.net 2.0 and Ajax

#21

Evan Freeman wrote:

Quote:

Well asp.net and apache aside, AJAX really has very little to do with both
of them per say.

SO whats AJAX, the web browser makes an httprequest, via <insert browser
implementation here>XmlHttpRequest object, either com or whatever.

All this does is make a call to a url and expects back some fragment in the
form of , html, json, xml, plain text, and whatever else you want to return.

So I would say if the request is being sent to apache there should be a way
to see it being made and being recieved, and I would guess failing somewhere
along that path.

My suggestions are thus:
1. Try using standard tools to track it down. If you use IE get fiddler.net,
if you use FireFox use firebug. those will let you see the requests being
sent out and any failures. Failures could be
the request times out or some error returned. 500, 401, 404, basic http
errors and the like.

2. cleanout the apache logs, or turn on logging, and setup a test fire the
ajax request and see if its getting logged as being recieved, and again look
for errors or the return.

My previous suggestions where along the same lines as the previous poster,
mostly an assumption you didn't have asp.net working. But if you do then its
nothing to do with ajax failures. AJAX is just a way of doing things not a
package or anything you need to install its just a way for a browser to make
a call out and return data in a threaded fashion so you don't need to
refresh the page just inject new elements into the DOM and let the browser
render them without a postback or fetch.

Hope this helps.

No I'm sorry it doesn't help. I'm so lost right now. I just hate Ajax

#22

Evan Freeman wrote:

Quote:

Well asp.net and apache aside, AJAX really has very little to do with both
of them per say.

SO whats AJAX, the web browser makes an httprequest, via <insert browser
implementation here>XmlHttpRequest object, either com or whatever.

All this does is make a call to a url and expects back some fragment in the
form of , html, json, xml, plain text, and whatever else you want to return.

So I would say if the request is being sent to apache there should be a way
to see it being made and being recieved, and I would guess failing somewhere
along that path.

My suggestions are thus:
1. Try using standard tools to track it down. If you use IE get fiddler.net,
if you use FireFox use firebug. those will let you see the requests being
sent out and any failures. Failures could be
the request times out or some error returned. 500, 401, 404, basic http
errors and the like.

2. cleanout the apache logs, or turn on logging, and setup a test fire the
ajax request and see if its getting logged as being recieved, and again look
for errors or the return.

My previous suggestions where along the same lines as the previous poster,
mostly an assumption you didn't have asp.net working. But if you do then its
nothing to do with ajax failures. AJAX is just a way of doing things not a
package or anything you need to install its just a way for a browser to make
a call out and return data in a threaded fashion so you don't need to
refresh the page just inject new elements into the DOM and let the browser
render them without a postback or fetch.

Hope this helps.

No I'm sorry it doesn't help. I'm so lost right now. I just hate Ajax

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

asp.net 2.0 and Ajax

ASP.net Web Controls microsoft.public.dotnet.framework.aspnet.webcontrols

Re: asp.net 2.0 and Ajax - 06-22-2008 , 10:14 PM

Re: asp.net 2.0 and Ajax - 06-22-2008 , 10:14 PM