Thanks John. At least that gives me an idea of what I have to do. I'll see if I can pursue that avenue. Not sure but I think David Adam's book had an example of receiving in chunks. Damn I think I got ri of the book a few years ago.
I'm still curious as to why 4D chose to give us 2GB limit but not the ability to do it regardless of fragmented RAM. Cheers 4D Tech mailing list wrote >> On Jan 8, 2020, at 4:15 PM, Jim Labos - infobase via 4D_Tech < > 4d_tech@.4d >> wrote: >> >> No I am using just plain File object to send file. On the 4D side I use >> WEB >> Get body part count and WEB GET BODY PART. No chunking that I know of >> unless >> 4D is doing itself (which by the way I don't know why they didn't >> implement >> that themselves since they give us a 2GB limit). > > The client and the server have to agree on sending with the chunked > protocol. This is obviously not supported by WEB GET BODY PART. That means > you would have to code the transfer yourself using WEB GET HTTP BODY > (using chunked encoding) and then you will have to parse the multi-part > form yourself because you can't use WEB GET BODY PART. > > I did something like this aeons ago using ITK before 4D's web server was > implemented. Even if I could find the code, I don't think it would be much > help. > > John DeSoi, Ph.D. > > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto: > 4D_Tech-Unsubscribe@.4D > ********************************************************************** ----- Jim Labos - infobase -- Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
