Steve Gerrard wrote:
"Dag Sunde" <me@dagsunde.co mwrote in message
news:45******** *************** @news.wineasy.s e...
<snipped/>
>>
So if you send a short request like "getHiscores.as p?limit=all",
and that results in a .responseText being 900K lonk, that
is not a problem, and no special consideration needs to be made.
Ooh, I like it, 100K seems like decent amount to be able to post, and
it looks like sending multiple blocks is not much more work. I have
been ducking away from doing some of this, but the time is rapidly
approaching. Thanks for the answers and the examples and the "oh it
is really no trouble at all" breezy attitude. I'm sure there will be
a little swearing along the way, but I feel much more confident about
making it work.
From the example in your other post:
<?xml version="1.0"?>
<root>
<rev_string>.uo yknahT</rev_string>
</root>
LOL
If you get into trouble, swear in my direction, and I'll try
to help you out...
That reminds me... Here is the Reverse.asp script:
<%@ Language=VBScri pt %>
<%Response.Buff er = True%>
<%
Response.Conten tType = "text/xml"
Response.CacheC ontrol = "Private"
Response.AddHea der "Cache-Control", "no-cache"
Dim testString
testString = Request.Form("t estString")
testString = StrReverse(test String)
Response.Write( "<?xml version='1.0' encoding='iso-8859-1'?>" )
Response.Write( "<root>" & vbCrLf)
Response.Write( "<rev_strin g>" & testString & "</rev_string>" & vbCrLf )
Response.Write( "</root>" & vbCrLf)
Response.End()
%>
The reason for setting the contenttype to "text/xml" is to tell the
xmlhttp object that it will get xml-data back, and that it should
be able to fill its .responeXml attribute with a DOM tree.
Note that you then have to .Write well-formed xml back to it.
I often use plaintext instead:
Response.Write( testString )
Response.End()
In this case, the .responseXML will be empty (no valid xml),
but use the .responseText instead (on the client side).
--
Dag.