>Hi Geore,
>
>Thank you for the reply!
>I agree with you about sending all the information once. My problem is that I need to access my business object (VFP COM DLL) through the Internet. In oder to do that, I have a common interface that I use to centralize all the accesses from my clients (I have Web interface - ASP, Offline application - VFP EXE and Palm devices). This interface is a HTTP request with parameters. Something like the following:
>
>http://myserver/InsertHeader.asp?date=01/01/2000&customer=001
>http://myserver/InsertItem.asp?&ProdID=001&qty=10&price=20.00
>
>Ok, I can imagine passing all this information in one call. I could pass a XML string as the unique parameter and this way I can handle all my different clients, forcing them only to build the XML string and doing all the work in my ASP page and my VFP DLL.
>
>Now a dumb question: Is there any restriction on the size a HTTP parameter can assume? I can have a very long XML string to pass. Is this a problem? can I manipulate this kind of "uploading" more efficiently?

HTTP POSTs can be as long as they need to be as long as the Web Server doesn't time out. However, it's a really bad idea to send huge amounts of data up all at once while leaving the user sitting staring at the screen.

You may have to come up with a way to chunk the data up to the server and then have a final routine that goes off and runs the full result data.