[google-appengine] Re: Why is GAE not popular?

[Vitaly Bogomolov]

Hi, Torsten,

My 5 cents.

GAE allows measure "quality of code" in money. If the code is "bad", you 
need a lot of GAE resources -> lot of money for serving your app.

This thing for some reason not liked by most developers.

:)

WBR, Vitaly.

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/b347a0bf-4026-4dbc-9de6-698416c7acfe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: All Managed VMs beta instances were turned down in the past hours.

[Jianliang Zhao]

Reported an issue: https://issuetracker.google.com/issues/68727696

On Tuesday, October 31, 2017 at 4:38:30 PM UTC-7, Jianliang Zhao wrote:
>
> According to this page: 
> https://cloud.google.com/appengine/docs/flexible/java/upgrading, the 
> shutdown of managed VMs will be 12/15/2017. Why is it started all of a 
> sudden?
>
> *Beta decommission date: December 15th, 2017*
>
> On December 15th, 2017, the Managed VMs environment (vm:true) will be 
> shut down and all apps using the beta vm:true configuration will stop 
> receiving traffic.
>
>
>
> On Tuesday, October 31, 2017 at 3:37:09 PM UTC-7, Justin Yip wrote:
>>
>> Hi,
>>
>> My company has multiple instances running on AppEngine. Since 2:38pm PST, 
>> we notices that *all* Managed VMs beta instances (*vm: true*) across 
>> multiple projects were turned down by "
>> apphosting-managed-vm-turnd...@system.gserviceaccount.com". See 
>> screenshot 
>> 
>> .
>>
>> On the other hand, instances with env: flex are not affected.
>>
>> We are able to restart these instances, but we wonder what is happening. 
>> We are aware that (vm: true) will be deprecated later this year. But we are 
>> not aware that instances will be turned off today (Oct 31).
>>
>> I am curious to see if anyone else has experienced the same issue.
>>
>> Thanks!
>>
>> Justin
>>
>>
>>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/21872195-1654-4f44-babe-827a030c93f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: All Managed VMs beta instances were turned down in the past hours.

[Jianliang Zhao]

According to this 
page: https://cloud.google.com/appengine/docs/flexible/java/upgrading, the 
shutdown of managed VMs will be 12/15/2017. Why is it started all of a 
sudden?

*Beta decommission date: December 15th, 2017*

On December 15th, 2017, the Managed VMs environment (vm:true) will be shut 
down and all apps using the beta vm:true configuration will stop receiving 
traffic.



On Tuesday, October 31, 2017 at 3:37:09 PM UTC-7, Justin Yip wrote:
>
> Hi,
>
> My company has multiple instances running on AppEngine. Since 2:38pm PST, 
> we notices that *all* Managed VMs beta instances (*vm: true*) across 
> multiple projects were turned down by "
> apphosting-managed-vm-turnd...@system.gserviceaccount.com ". 
> See screenshot 
> 
> .
>
> On the other hand, instances with env: flex are not affected.
>
> We are able to restart these instances, but we wonder what is happening. 
> We are aware that (vm: true) will be deprecated later this year. But we are 
> not aware that instances will be turned off today (Oct 31).
>
> I am curious to see if anyone else has experienced the same issue.
>
> Thanks!
>
> Justin
>
>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/41def010-9009-4809-8efe-62c8c98cbece%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: 413 NGINX error on large file uploads

[Scott Campbell]

Hey Yannick,

Thanks for your input.

In the case that I need to upload files that are larger than 32 MB, what 
are my options?  I was hoping to upload to cloud storage using my app.  It 
was the reason I built it haha.


On Tuesday, October 31, 2017 at 3:32:05 PM UTC-4, Yannick (Cloud Platform 
Support) wrote:
>
> Hello Scott, an App Engine application cannot receive inbound requests 
> that are larger than 32MB 
> . This limit cannot 
> be increased.
>
> In order to store large files, you should instead upload them directly to 
> Cloud Storage. Resumable uploads 
>  
> are 
> a good way to handle the upload of large files.
>
> On Tuesday, October 31, 2017 at 9:01:20 AM UTC-4, Scott Campbell wrote:
>>
>> Hey Everyone,
>>
>> Hoping to get some help, as there doesn't seem to be much support in the 
>> Google docs regards the NGINX configuration when running an app in Google 
>> App Engine.
>>
>> My app is running fine, but I get this 413 error when I try and upload an 
>> audio file (.wav or .mp3).
>>
>> "413 Request Entity Too Large -- nginx "
>>
>>
>> My app is running Django, with Cloud PostSQL and Cloud Storage enabled.
>>
>>
>> I researched the error, and it seems I can set an NGINX config setting 
>> *"client_max_body_size 
>> 20M" *but like I said, there is no documentation regaring how to 
>> manually config NGINX on deploy.
>>
>> Does anybody have any idea what is going on?  Any suggestions?
>>
>>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/fff119f7-f2cc-4495-8072-844493154548%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] All Managed VMs beta instances were turned down in the past hours.

[Justin Yip]

Hi,

My company has multiple instances running on AppEngine. Since 2:38pm PST, 
we notices that *all* Managed VMs beta instances (*vm: true*) across 
multiple projects were turned down by 
"apphosting-managed-vm-turnd...@system.gserviceaccount.com". 
See screenshot 

.

On the other hand, instances with env: flex are not affected.

We are able to restart these instances, but we wonder what is happening. We 
are aware that (vm: true) will be deprecated later this year. But we are 
not aware that instances will be turned off today (Oct 31).

I am curious to see if anyone else has experienced the same issue.

Thanks!

Justin


-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/ae35aec8-70e6-44f9-8d38-cb2014f5e338%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: A lot of instability in Google App Engine Standard today

['Kenworth (Google Cloud Platform)' via Google App Engine]

Link to the Public Issue Tracker .

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/77cbceeb-b116-4df7-b381-b61d4e63c5d6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: [Google Cloud Insiders] A lot of instability in Google App Engine Standard today

[PK]

Many thanks to Rahul who jumped in and addressed the issue for my affected 
project. 

It turns out, this was another manifestation of this issue 
 that needs to be addressed. 
(Basically, Google rolled out a new runtime to a percentage of the running 
instances, there was a problem with the new runtime so requests to the canary 
instances fail and I had to realize it and inquire, and then Google puts all 
the project's instances back to the old runtime until they address the issue 
and try again)….

Please star the issue before it happens to you, it is rare but when it happens 
is not fun...


> 
> Hello,
>   What is your app-id where you are seeing this?
> Thanks,
> ~Rahul.
> 
> On Tue, Oct 31, 2017 at 1:37 PM, PK  > wrote:
> Many requests fail, usually Ajax calls but I just got one in the UI. I am in 
> US Central/python runtime anybody else experiencing instability?
> 
> Error: Server Error
> 
> The server encountered an error and could not complete your request.
> Please try again in 30 seconds.
> 
> 
> 
> 
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Google Cloud Insiders" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to google-cloud-insiders+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to google-cloud-insid...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/google-cloud-insiders 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-cloud-insiders/1F1EA516-B410-4EE7-ABFA-06E5E704F100%40gae123.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .
> 

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/5ECD2F32-3989-487B-9552-9C4663485DA5%40gae123.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: [Google Cloud Insiders] A lot of instability in Google App Engine Standard today

['Rahul Ravindran' via Google App Engine]

Hello,
  What is your app-id where you are seeing this?
Thanks,
~Rahul.

On Tue, Oct 31, 2017 at 1:37 PM, PK  wrote:

> Many requests fail, usually Ajax calls but I just got one in the UI. I am
> in US Central/python runtime anybody else experiencing instability?
>
> Error: Server ErrorThe server encountered an error and could not complete
> your request.
>
> Please try again in 30 seconds.
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Cloud Insiders" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-cloud-insiders+unsubscr...@googlegroups.com.
> To post to this group, send email to google-cloud-insiders@
> googlegroups.com.
> Visit this group at https://groups.google.com/group/google-cloud-insiders.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-cloud-insiders/1F1EA516-B410-4EE7-ABFA-
> 06E5E704F100%40gae123.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/CALZe7H0XKd0FdtAPEVSEPf05VXb6qCANWm%3DP0T9XGhSg0WzrxQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] A lot of instability in Google App Engine Standard today

[PK]

Many requests fail, usually Ajax calls but I just got one in the UI. I am in US 
Central/python runtime anybody else experiencing instability?

Error: Server Error

The server encountered an error and could not complete your request.
Please try again in 30 seconds.






-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/1F1EA516-B410-4EE7-ABFA-06E5E704F100%40gae123.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Reaching a quota limit for the Android Oauth2 Client ID

[Yosi Dediashvili]

Hi,

We're managing more than 100 apps with google login on Android but using 
the same SDK client ID on all of them. This means that we need to register 
every single app separately with its appropriate *package name *under:

API & Services > Credentials > Create Credentials > OAuth client ID > 
Android

The issue is that recently, we got an error while trying to add a new app, 
claiming that we reached the number of allowed clients: 
This project has reached its maximum number of OAuth clients. To create 
another, first remove an existing one.


















Did any one else get such an error? Does Google support increasing that 
limit?

Thanks!

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/454b3f5d-38e4-4713-ac65-b27619b4e5ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: 413 NGINX error on large file uploads

['Yannick (Cloud Platform Support)' via Google App Engine]

Hello Scott, an App Engine application cannot receive inbound requests that are 
larger than 32MB . This 
limit cannot be increased.

In order to store large files, you should instead upload them directly to 
Cloud Storage. Resumable uploads 
 
are 
a good way to handle the upload of large files.

On Tuesday, October 31, 2017 at 9:01:20 AM UTC-4, Scott Campbell wrote:
>
> Hey Everyone,
>
> Hoping to get some help, as there doesn't seem to be much support in the 
> Google docs regards the NGINX configuration when running an app in Google 
> App Engine.
>
> My app is running fine, but I get this 413 error when I try and upload an 
> audio file (.wav or .mp3).
>
> "413 Request Entity Too Large -- nginx "
>
>
> My app is running Django, with Cloud PostSQL and Cloud Storage enabled.
>
>
> I researched the error, and it seems I can set an NGINX config setting 
> *"client_max_body_size 
> 20M" *but like I said, there is no documentation regaring how to manually 
> config NGINX on deploy.
>
> Does anybody have any idea what is going on?  Any suggestions?
>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/621d128f-a639-470b-8084-87739d751458%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: PHP app engine cannot connect to cloud sql

[Attila-Mihaly Balazs]

I'm no PHP expert, but I believe that for mysqli_connect to work with Unix 
Domain Sockets, one must specify "localhost" for the host and the socket as 
the last parameter. From here: https://stackoverflow.com/a/13771199/1265

The syntax would be: mysqli_connect("localhost", 
$dbuser_prod,$dbpass_prod,$dbname_prod, $socket_prod);

Also, take care that you're $socket_prod contains an extra ":" at the start.

Regards,
Attila

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/46bfec06-5792-4222-972e-598e866a17e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: App Engine closed local connection on Cloud sql

['Jordan (Cloud Platform Support)' via Google App Engine]

As described in the blue 'Note' in the documentation 
, your 
instance type is PostgreSQL and connections from App Engine to PostgreSQL 
are not currently supported in the App Engine Standard environment. 

Our engineering team is aware of this 
 and are currently working on 
supporting this. You may actually have luck if you are making connections 
from the new Java 8 App Engine standard runtime 
.

- Since Google Groups is meant for general product discussions and not for 
technical support or for reporting issues or feature requests, it is 
recommended in the future to report Google-end issues and feature requests 
to the Public Issue Tracker 
 and to seek 
technical support on Stack Overflow 
 using the supported 
Cloud tags.  

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/7e399fc4-a9cd-4c6e-a3fe-72d1986dd14e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: i am being charge like hell on flex app engine for laravel 5.5

['Yannick (Cloud Platform Support)' via Google App Engine]

Your charges reflect the resources you have been using and/or explicitly 
reserving, which included several Flex instances running at all times. You 
should be sure to delete or disable any resources you are not actually 
using.

As for App Engine Standard, it has the ability to scale down to zero 
instances, meaning zero cost, when it receives no requests for a period of 
time. If your application receives low traffic it could very well be the 
lowest cost option. Read this comparison of both environments 
 to 
help decide which one is best for you.

On Monday, October 30, 2017 at 5:18:27 PM UTC-4, Tariq Sajid wrote:
>
> I dont know why but so much is* being charge* right now i choose the 
> japan region and just started the sql but not used it but still my billing 
> charges is too much please look at the screenshot
> my question is if i choose *standard environment* will the charging will 
> be less ?
>
>
> 
>
>
>
>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/45498eb1-c6a9-4bf8-b132-8f91199c403a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Session Management

['Yannick (Cloud Platform Support)' via Google App Engine]

The exact technical details of session support are not publicly documented, 
but the appengine-web.xml Reference 

 you 
pointed to before does say it stores the data on the Datastore with 
Memcache acting as a speed boost. That is to say it stores it in the same 
way you should be storing session data if you were to handle it yourself.

And no, at this time this system only supports valid Google accounts, which 
are gmail.com accounts or a GSuite domain's accounts.

On Tuesday, October 31, 2017 at 6:34:21 AM UTC-4, Joshua Fox wrote:
>
>
>
>  
>
>>
>> Note that session support is something that is done per-runtime and 
>> per-framework, 
>>
>
> I am asking specifically about Google Application Engine Standard 
> Environment Java 7; and for Java 8. 
>
> but most if not all of them include it as it is indeed a basic feature of 
>> a web server. Part of the Bookshelf tutorial deals with using sessions 
>> 
>> .
>>
>
> Thank you. I see that that indeed supports  req.getSession().setAttribute(
> ...)
>
> How is this data stored so that it is accessible to all Instances? In the 
> Memcache?
>
> Apparently this uses the Users API 
> , 
> which works with Google or OAuth authentication. Does GAE Standard Env use 
> a Session Store, accessible for all Instances, which is usable with 
> user-authentication in general? According to this StackOverflow answer 
> ,  it does not.
>
>>
>>
>> On Monday, October 30, 2017 at 3:30:28 AM UTC-4, Joshua Fox wrote:
>>>
>>> What is the recommended way to do Session Management on Google 
>>> Application Engine? 
>>>
>>> In the webapp world, the usual implementation with a session store 
>>> (Redis/Memcache/RDBMS etc) that is shared by all server-instances.
>>>
>>> So, when the Java code calls
>>>
>>>  request.getSession().setAttribute("UserName", username);
>>>
>>>   that value will be accessible for multiple 
>>> requests by this browser.
>>>
>>> A websearch shows some advice: 
>>>
>>>- Implement it yourself 
>>>- Various  open-source libraries, non-standard and mostly 
>>>unmaintained 
>>>
>>> I would expect a PaaS like GAE to have  Session Management 
>>>  out-of-the-box. 
>>>
>>> This StackOverflow answer 
>>> 
>>>  says "AppEngine 
>>> uses Datastore to store the session informations and memcache for faster 
>>> access" and this official documentation  
>>>  
>>> mentions that 
>>> "Session data is always written synchronously to memcache." 
>>>
>>> But on the other hand this tutorial  
>>> 
>>>  suggests  
>>> that  session management must be added to GAE.
>>>
>>> How should we do Session Management?
>>>
>>>
>>> -- 
>> 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 google-appengine+unsubscr...@googlegroups.com.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> 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/764e06ad-4d90-45bd-8bcd-e801913976a0%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
>  
>
> *JOSHUA FOX*
> Principal Software Architect | Freightos
>
>
>
> *T (Israel): *+972-545691165 | *T (US)*:  +1-3123400953  
> Smooth shipping.
>
>
>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/87537ad8-948e-46cc-8e6d-4945e10604ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] 413 NGINX error on large file uploads

[Scott Campbell]

Hey Everyone,

Hoping to get some help, as there doesn't seem to be much support in the 
Google docs regards the NGINX configuration when running an app in Google 
App Engine.

My app is running fine, but I get this 413 error when I try and upload an 
audio file (.wav or .mp3).

"413 Request Entity Too Large -- nginx "


My app is running Django, with Cloud PostSQL and Cloud Storage enabled.


I researched the error, and it seems I can set an NGINX config setting 
*"client_max_body_size 
20M" *but like I said, there is no documentation regaring how to manually 
config NGINX on deploy.

Does anybody have any idea what is going on?  Any suggestions?

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/1f2fa910-6755-4924-a53f-3b977631854a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Session Management

[Joshua Fox]

>
> Note that session support is something that is done per-runtime and
> per-framework,
>

I am asking specifically about Google Application Engine Standard
Environment Java 7; and for Java 8.

but most if not all of them include it as it is indeed a basic feature of a
> web server. Part of the Bookshelf tutorial deals with using sessions
> 
> .
>

Thank you. I see that that indeed supports  req.getSession().setAttribute(
...)

How is this data stored so that it is accessible to all Instances? In the
Memcache?

Apparently this uses the Users API
, which
works with Google or OAuth authentication. Does GAE Standard Env use a
Session Store, accessible for all Instances, which is usable with
user-authentication in general? According to this StackOverflow answer
,  it does not.

>
>
> On Monday, October 30, 2017 at 3:30:28 AM UTC-4, Joshua Fox wrote:
>>
>> What is the recommended way to do Session Management on Google
>> Application Engine?
>>
>> In the webapp world, the usual implementation with a session store
>> (Redis/Memcache/RDBMS etc) that is shared by all server-instances.
>>
>> So, when the Java code calls
>>
>>  request.getSession().setAttribute("UserName", username);
>>
>>   that value will be accessible for multiple requests
>> by this browser.
>>
>> A websearch shows some advice:
>>
>>- Implement it yourself
>>- Various  open-source libraries, non-standard and mostly
>>unmaintained
>>
>> I would expect a PaaS like GAE to have  Session Management
>>  out-of-the-box.
>>
>> This StackOverflow answer
>> 
>>  says "AppEngine
>> uses Datastore to store the session informations and memcache for faster
>> access" and this official documentation
>>  
>> mentions that
>> "Session data is always written synchronously to memcache."
>>
>> But on the other hand this tutorial
>> 
>>  suggests
>> that  session management must be added to GAE.
>>
>> How should we do Session Management?
>>
>>
>> --
> 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 google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> 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/764e06ad-4d90-45bd-8bcd-
> e801913976a0%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 


*JOSHUA FOX*
Principal Software Architect | Freightos



*T (Israel): *+972-545691165 | *T (US)*:  +1-3123400953
Smooth shipping.

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/CAD%3DB7cO6rGKBRy3wNwUFDJ0c20HArrrnPemcyh6KM56%2BmpgF6g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Why is GAE not popular?

[Richard Cheesmar]

Hi, Torsten, 

Google App Engine was, I suspect, originally adopted by Python and Java 
developers in the early days,  it was seen as a very cheap alternative as a 
Paas. Based around the no-sql datastore, it offered quite a few advantages 
to say the heavy-ish load of say a straight Django based server option. The 
whole Paas idea being to relinquish the substantial dev-ops requirements 
that often burdened smaller developers. Today it is a different beast, it's 
no longer a matter of the Standard environment and Java or Python. You have 
the Flex environment, extra lnagues, Go and PHP in the mix as well as 
numerous APIs and cloud facilities that can really help speed up 
development of any size projects. Developing restful APIs as micro-services 
for example, cloud storage, and many cloud based facilities are now part of 
the overall development ecosystem. 

Today I don't think you should look at google-app-engine development just 
in terms of the core code base. It's part of an family of tools that I 
personally use most everyday. It still has it's issues, documentation for a 
a long while was in need of improvement but it's getting much better all 
the time. On the downside, the requirement to get to grips with the various 
components Google now offers can be quite time consuming and the original 
concept of getting rid of the burden of heavy dev-ops has since been 
somewhat retograde by the need to understand, use and monitor all the 
activities of a web site via the cloud console and other tools. To be fair 
though, this is more to do with the reality of designing web apps which are 
no longer small and simple. The web today is a complex beast, which many 
people underestimate when it comes to tooling up and development, but 
Google is getting much better as it matures and takes away many of the more 
painful and cumbersome burdens that modern web app development brings.

I wholeheartedly recommend it.

If you need some advice of any form give me a shout.



On Monday, October 23, 2017 at 4:03:33 PM UTC+3, Torsten Därr wrote:
>
> Hi, I'm not a web developer but I've been running websites for many years 
> having them created by web development companies. I've been trying to find 
> a good company that is familiar with Google App Engine because I do believe 
> that the Google ecosystem is the right choice for my next sites and 
> projects. Can you give me any idea as to how I can find a web developing 
> company that has been using Google App Engine for a while successfully? 
> Many thanks, Torsten
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/697030d3-8067-4175-b3fc-9bdb3b0f2c19%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.