Well, the problem with that is that the application that I'm building
is mean't for internal use only and it would be against my companies
policies to make it public. I'm really not doing anything outside of
the box here. My page does return a lot of html and I think the browser
just runs out of memory. It seems to crash when the DOM parser comes
into play.
Here is the function I wrote though to update my container. Maybe
you'll see something unusual:
function ajaxUpdater(mForm,mUrl,mMethod,outputObj) {
var params = '';
if(mForm) {
params=customSerializer(mForm)+'&time='+currentTime();
} else { params = '?time=' + currentTime(); }
var ajax = new Ajax.Updater({
success: outputObj},mUrl,{
evalScripts:true, method: mMethod, parameters: params,
onFailure: function(response) {
reportError(response.responseText);
}
});
}
------------------------------------------------------------------------------------------
and I call it like so
------------------------------------------------------------------------------------------
ajaxUpdater('','viewer.asp','get','contentPanel');
------------------------------------------------------------------------------------------
Pretty simple. Lemme know if you spot anything unusual.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---
