Re: [google-appengine] Re: Node.js standard and urlfetch

But yes, you're correct. Only for me is more important a streaming between the client and the my app. вт, 10 июл. 2018 г., 23:40 Aleksander Efremov : > > https://cloud.google.com/appengine/docs/standard/nodejs/how-requests-are-handled > > Streaming Responses > > App Engine does not support stream

Re: [google-appengine] Re: Node.js standard and urlfetch

https://cloud.google.com/appengine/docs/standard/nodejs/how-requests-are-handled Streaming Responses App Engine does not support streaming responses where data is sent in incremental chunks to the client while a request is being processed. All data from your code is collected as described above a

Re: [google-appengine] Re: Node.js standard and urlfetch

Streaming doesn't work for inbound requests (i.e., requests from a client to your App Engine app), but should work fine for outbound requests originating from your App Engine app to another server. On Mon, 9 Jul 2018 at 22:11 Aleksander Efremov wrote: > Yes, I use `http`/`https` native librarie

Re: [google-appengine] Re: Node.js standard and urlfetch

Yes, I use `http`/`https` native libraries and I use streaming of course when it's possible. But as I understood from the AppEngine documentation, streaming doesn't work and all responses are buffered in any case. Do you know why streaming isn't ready yet and when it will possible? On Monday,

Re: [google-appengine] Re: Node.js standard and urlfetch

For nodejs8, you do not need the Sockets API. In fact, it's not even possible. Just connect to other servers like you would in a VM environment. On Mon, Jul 9, 2018 at 12:35 PM Attila-Mihaly Balazs wrote: > ^^^ This. > > However, Steren, please correct me if I'm wrong but I believe that to use >

Re: [google-appengine] Re: Node.js standard and urlfetch

As a workaround to this, you can use the Blobstore API which allows users to upload large files through an HTML form. The browser uploads and stores the file directly to the Blobstore then rewrites the user's request. The data is sent using blob keys to the URL path specified. The documentation

Re: [google-appengine] Re: Node.js standard and urlfetch

^^^ This. However, Steren, please correct me if I'm wrong but I believe that to use the "idiomatic methods to send asynchronous requests to HTTP endpoints" one needs to enable "sockets": https://cloud.google.com/appengine/docs/standard/python/sockets/ (and also needs to be a paying application

Re: [google-appengine] Re: Node.js standard and urlfetch

Hi, As commented on the bug: It is not clear what problem a Node.js implementation of urlfetch would solve. Today, developers can use idiomatic methods to send asynchronous requests to HTTP endpoints, for example by using the native `http` module. Did you try it? Steren Product Manager App Engine

Re: [google-appengine] Re: Node.js standard and urlfetch

oh, yes, it's important note, thanks. On Friday, July 6, 2018 at 6:58:38 PM UTC+4, Jeff Schnitzer wrote: > > There's one big disadvantage of the URLFetch service, which is that it's > limited to 32MB inbound and 10MB outbound. Those are pretty small numbers > in this day and age. > > In Java8-la

Re: [google-appengine] Re: Node.js standard and urlfetch

There's one big disadvantage of the URLFetch service, which is that it's limited to 32MB inbound and 10MB outbound. Those are pretty small numbers in this day and age. In Java8-land I've used both Apache HttpClient and OkHttp and both work normally. Jeff On Thu, Jul 5, 2018 at 10:06 PM Aleksande

[google-appengine] Re: Node.js standard and urlfetch

Thanks, then I will star of course that feature request. And it's very good there isn't difference. On Thursday, July 5, 2018 at 11:58:27 PM UTC+4, Yasser Karout (Cloud Platform Support) wrote: > > Currently, there is no implementation of urlfetch for Node.js so you would > have to use the stan

[google-appengine] Re: Node.js standard and urlfetch

Currently, there is no implementation of urlfetch for Node.js so you would have to use the standard HTTP library or other libraries to issue HTTP requests. I created a feature request on the issue tracker website whi

[google-appengine] Re: Node.js standard and urlfetch

I more want to know there are restrictions on fetching arbitrary URLs via "urlfetch" or "native libraries"? I rewrote the Go (was used the "urlfetch" service) implementation of the proxy service to Node.js (uses native http/https libraries) and I want to be sure a performance didn't change. On

[google-appengine] Re: Node.js standard and urlfetch

I believe (but I'm not 100%) that the new runtimes (node.js, Java 8, Python 3.7 in beta, etc) are moving AppEngine standard more towards Flex. Ie. they will be full containers (thought managed and updated by Google) where you can install arbitrary binaries. This means that they don't/won't need