Originally Posted by Skyzyx
I appreciate the kind of flexibility you're trying to provide with this solution, but I seriously have to question whether this is the right way to accomplish that... and I can't, in good conscience, recommend a method that does away with best practices for a method that functions in complete absence of a semantically-valid mindset.
Sorry to sound so negative after you've obviously put a lot of work into this, but this is like trying to heal a wound with lemon juice. It's the wrong tool for the job.
i made this drawing from my experiences with ajax.
this is certainly to be considered an alternate transport.
the origional need was to put unparsed raw text right into code, without having to tediously escape it. this is good for documentation and templating.
i would recommend always using the best method available.
but there are times when xmlHTTRequests cannot be used.
this is something you can use in places where existing solutions fall short.