Re: HTTP Upload file size too low

2020-01-08 Thread Jim Labos - infobase via 4D_Tech
I wish. However as someone else pointed out some IT departments will not
allow FTP. The people who would be using this are not predetermined so I
have no way of knowing or vetting FTP.

Cheers


Just curious could you not code something so that it uses FTP?

Regards

Chuck

 Chuck Miller Voice: (617) 739-0306
 Informed Solutions, Inc. Fax: (617) 232-1064   
 mailto:cjmillerinformed-solutions.com 
 Brookline, MA 02446 USA Registered 4D Developer
   Providers of 4D and Sybase connectivity
  http://www.informed-solutions.com  

This message and any attached documents contain information which may be
confidential, subject to privilege or exempt from disclosure under
applicable law.  These materials are intended only for the use of the
intended recipient. If you are not the intended recipient of this
transmission, you are hereby notified that any distribution, disclosure,
printing, copying, storage, modification or the taking of any action in
reliance upon this transmission is strictly prohibited.  Delivery of this
message to any person other than the intended recipient shall not compromise
or waive such confidentiality, privilege or exemption from disclosure as to
this communication. 



**
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
**

Re: HTTP Upload file size too low

2020-01-08 Thread Jim Labos - infobase via 4D_Tech
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
**

Re: HTTP Upload file size too low

2020-01-08 Thread Chuck Miller via 4D_Tech
Just curious could you not code something so that it uses FTP?

Regards

Chuck

 Chuck Miller Voice: (617) 739-0306
 Informed Solutions, Inc. Fax: (617) 232-1064   
 mailto:cjmillerinformed-solutions.com 
 Brookline, MA 02446 USA Registered 4D Developer
   Providers of 4D and Sybase connectivity
  http://www.informed-solutions.com  

This message and any attached documents contain information which may be 
confidential, subject to privilege or exempt from disclosure under applicable 
law.  These materials are intended only for the use of the intended recipient. 
If you are not the intended recipient of this transmission, you are hereby 
notified that any distribution, disclosure, printing, copying, storage, 
modification or the taking of any action in reliance upon this transmission is 
strictly prohibited.  Delivery of this message to any person other than the 
intended recipient shall not compromise or waive such confidentiality, 
privilege or exemption from disclosure as to this communication. 

> On Jan 8, 2020, at 8:44 PM, John DeSoi via 4D_Tech <4d_tech@lists.4d.com> 
> wrote:
> 
> 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-unsubscr...@lists.4d.com
**

Re: HTTP Upload file size too low

2020-01-08 Thread John DeSoi via 4D_Tech

> On Jan 8, 2020, at 4:15 PM, Jim Labos - infobase via 4D_Tech 
> <4d_tech@lists.4d.com> 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-unsubscr...@lists.4d.com
**

Re: HTTP Upload file size too low

2020-01-08 Thread Jim Labos - infobase via 4D_Tech
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).

That was my question before: Anyone have access to code samples/examples on
how to do it with chunks.









-
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
**

RE: HTTP Upload file size too low

2020-01-08 Thread Jim Labos - infobase via 4D_Tech
Good to know that but from what I've read I'm not the only one having this
issue with inconsistent size uploads. I also get the same error others are
getting.

I'm using the basic way to obtain the file in a Blob in 4D by using WEB Get
body part count and WEB GET BODY PART to get the Blob.

I get the Document name consistently but the Blob will be empty in some
cases.

Are you using the same methods to obtain the file or receiving in chunks?

Thanks




-
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
**

Re: HTTP Upload file size too low

2020-01-08 Thread John DeSoi via 4D_Tech

> On Jan 8, 2020, at 3:03 PM, Jim Labos - infobase via 4D_Tech 
> <4d_tech@lists.4d.com> wrote:
> 
> The only way to upload consistently without getting any errors supposedly is
> to do it in chunks. I am trying to find a way to do that. So far I could not
> find any code examples.

What client software is sending the response to 4D? Have you verified that it 
is (or can be configured to) send a chunked response? If you are using a HTML 
form with a standard file input, I could not find any evidence that it would 
automatically do chunking. Perhaps it does if the right headers are exchanged. 
I suggest answering this question before spending time trying to write server 
code to accept the chunked response.

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-unsubscr...@lists.4d.com
**

RE: HTTP Upload file size too low

2020-01-08 Thread Dennis, Neil via 4D_Tech
> Is anyone uploading files as large as 2GB to 4D?

I do up to 1GB, never had an issue.

Neil







Privacy Disclaimer: This message contains confidential information and is 
intended only for the named addressee. If you are not the named addressee you 
should not disseminate, distribute or copy this email. Please delete this email 
from your system and notify the sender immediately by replying to this email.  
If you are not the intended recipient you are notified that disclosing, 
copying, distributing or taking any action in reliance on the contents of this 
information is strictly prohibited.

The Alternative Investments division of UMB Fund Services provides a full range 
of services to hedge funds, funds of funds and private equity funds.  Any tax 
advice in this communication is not intended to be used, and cannot be used, by 
a client or any other person or entity for the purpose of (a) avoiding 
penalties that may be imposed on any taxpayer or (b) promoting, marketing, or 
recommending to another party any matter addressed herein.
**
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
**

RE: HTTP Upload file size too low

2020-01-08 Thread Jim Labos - infobase via 4D_Tech


This is a known issue due to fragmented memory as 4D will only use
contiguous memory for uploads. I do check with WEB GET OPTION(Web Maximum
requests size;$i_SET_SIZE) and $i_SET_SIZE is at the max setting of 2GB.

I'd be content with the 2GB limit. I can sometimes upload 500MB, others not
even 300MB. Next day 1GB is good then try again and it fails. The name of
the file comes in when calling "WEB GET BODY
PART($i;blb_FILE;object_name;txt_mime;fileName)" but the BLOB will be empty.

The only way to upload consistently without getting any errors supposedly is
to do it in chunks. I am trying to find a way to do that. So far I could not
find any code examples.

Is anyone uploading files as large as 2GB to 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
**