[jQuery] Re: Moving from .get(xml file) to using .ajax

2009-03-03 Thread KrushRadio - Doc
If thats all it was, i'm going to ROFLStomp my keyboard. Thanks for your wisdom. I thought i was going out of my mind for a second. ~Doc On Mar 3, 3:18 pm, mkmanning wrote: > Make URL lowercase: > ... > url:"kprxy.php", > ... > > On Mar 3, 9:50 am, KrushRadio - Doc wrote: > > > > > Okay.. Th

[jQuery] Re: Moving from .get(xml file) to using .ajax

2009-03-03 Thread mkmanning
Make URL lowercase: ... url:"kprxy.php", ... On Mar 3, 9:50 am, KrushRadio - Doc wrote: > Okay.. Thanks..I'll do that with the cache: false, thing. > > I still have the problem where it's not pulling the right data from > the xml, as it used to before.. > Any thoughts on that one, or if you can

[jQuery] Re: Moving from .get(xml file) to using .ajax

2009-03-03 Thread KrushRadio - Doc
Okay.. Thanks..I'll do that with the cache: false, thing. I still have the problem where it's not pulling the right data from the xml, as it used to before.. Any thoughts on that one, or if you can eyeball the second part of the code and let me know if there's something goofed? Thanks, Dan O

[jQuery] Re: Moving from .get(xml file) to using .ajax

2009-03-03 Thread mkmanning
You're still going to run into the issue of caching for requests to the same URL, even using ajax. The usual solution, as Ryan suggested, is to append changing data to the querystring of the ajax request, usually in the form of a timestamp: "the_querystring"+new Date ().getTime() As of jQuery 1.2

[jQuery] Re: Moving from .get(xml file) to using .ajax

2009-03-03 Thread KrushRadio - Doc
It should, but this is going to be an ajax application in the end.. I need to constantly pull it and display it on one page every 15 seconds On Mar 3, 3:17 am, "ryan.joyce...@googlemail.com" wrote: > if the browser is caching the query, would appending a parameter > containing a random number or

[jQuery] Re: Moving from .get(xml file) to using .ajax

2009-03-03 Thread ryan.joyce...@googlemail.com
if the browser is caching the query, would appending a parameter containing a random number or some such to the end of the request stop that?