FTP on AppEngine Standard is really not an option. It *can* work *sometimes*.
>From my experience, the underlying socket infrastructure does not always give you the same IP for each socket created (which makes sense when we consider the AppEngine automatic scalability features and how massively distributed the AppEngine infrastructure must be to offer such a promise). Given this, the FTP control and data connexions won't always have the same IP source, and thus will confuse the FTP server a lot. On Friday, February 10, 2017 at 12:39:51 AM UTC+1, Nick wrote: > > Sockets and Threads are both first class features of GAE, they should be > totally reliable. Historically appengine does suffer from network > configuration errors that don't get picked up unless they're heavily used > (i.e. geographical issues and unusual ports) - it seems monitoring is based > on error rates of total. But reporting them usually gets and investigation > and a fix. > > Socket usage is much more heavily affected by quota limitations - for > example using Apache HttpClient instead of URLFetch will net you problems > as you scale. But for your usage you should not expect to see any issues. > > > On Friday, February 10, 2017 at 8:50:35 AM UTC+11, Emanuele Ziglioli wrote: >> >> Thanks Nick >> >> I've checked out your code and it looks similar to other work I've done >> myself before, adapting apache commons so that it would use GAE's low level >> support for sockets. >> It did work for a while but then it stopped. When I complained about they >> told me simply that GAE don't support FTP, full stop: >> >> https://groups.google.com/forum/?fromgroups#!searchin/google-appengine/FTP%7Csort:date/google-appengine/mVVDE4wECbY/t4lEQDUzDQAJ >> >> Things like "More future-oriented people might resent having to use an >> FTP server" drive me furious, what about actually listening to customers >> (us)? >> Future-oriented people might resent using GAE standard. >> I could add a lot more but I guess our monthly bill is nothing so I'll >> shut up >> >> Emanuele >> >> On Thursday, 9 February 2017 10:47:06 UTC+13, Nick wrote: >>> >>> I have been able to get ftp working on appengine using software >>> libraries, you'll need to pick the write combo though, and it is a bit >>> sensitive to the server on the other end (i.e. Passive mode etc) >>> >>> If it's critical I suspect you'd be better off bringing another >>> component into your stack to deal with this from GCE or GKE. >>> >>> The source below will help you, it uses apache ftp client, which from >>> memory uses just sockets, so as long as you have billing enabled with >>> budget should be ok. I had to 'override' a bunch of the implementation for >>> GAE - unfortunately there was a decent amount of blacklisted calls without >>> extension points or declared final. >>> >>> https://github.com/atomicleopard/thundr-contrib-gae-ftp >>> >>> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/0e25e654-e70e-4fe5-843c-57386f0e3b40%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
