|
> From: Scott Klement > > I know that this comment isn't very helpful, but... that's HTML, not HTTP. > It's not part of the HTTP standard in any way. If it were HTTP, it would > look like "%3c" You're right... I really AM tired. What's really strange is that I don't get this behavior in Java. When I read the stuff through the Java API, the data gets "de-HTML-ized". Looking at the TCP/IP stream, though, I can see the embedded > encoding. So evidently the web services API is encoding and decoding the stream magically. I really hate magic APIs. > HTTPAPI should be able to return as much as 4gb in a single transfer, I > haven't had any problems with that limit yet. Okay, that makes sense. I actually was having more problem with the outbound side than the inbound side. But for the outbound buffer, HTTPAPI just takes a pointer and a length, and I suppose I can use a user space for that. I've not done much with user spaces, but my guess is they are contiguous, and that I can read the data into a user space and pass its address to HTTPAPI. In fact, I bet if I was smart and had my data in an IFS file that I could directly materialize a pointer to the IFS file and pass that, but that would require me being smart. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.