[google-appengine] Re: How to set deadline for a PHP URL fetch?

[1moretime]

Hi, Stuart
Thanks for your reply,
I tried following code, but failed.


$data = http_build_query($data);
$context =
array("http"=>
  array(
"method" => "POST",
"content" => $data,
//"header" => "Connection: keep-alive\r\n",
//"deadline" => 60, // The deadline can be up to a maximum
of 60 seconds for request handlers
"timeout" => 30 // GAE requests have a 30-second deadline
  )
);
$context = stream_context_create($context);

$result = file_get_contents($url, false, $context);




Still got same warning message in gae logs.



PHP Warning:  file_get_contents(..): failed to open
stream: Request deadline exceeded in /base/data/home/apps/.php
on line 93




Any suggestion?



On Jun 4, 5:56 pm, Stuart Langley  wrote:
> set the timeout value in the http context to the number of seconds you want
> the deadline to be.
>
>
>
>
>
>
>
> On Tuesday, 4 June 2013 12:05:29 UTC+10, 1moretime wrote:
>
> > Thanks, Dan
>
> > I read that doc but PHP version not found.
> > would you pls give some php code?
>
> > On Jun 4, 4:16 am, Dan Holevoet  wrote:
> > > This is a great question for the App Engine Stack Overflow
> > > tag,
> > > which also conveniently happens to have an
> > > answer<
> >http://stackoverflow.com/questions/2162115/how-to-set-timeout-for-url...>for
>
> > > you!
>
> > > Thanks,
> > > Dan
>
> > > On Mon, Jun 3, 2013 at 8:20 AM, 1moretime 
> > wrote:
> > > > URL Fetch overview says:
>
> > > > You can set a deadline for a request, the most amount of time the
> > > > service will wait for a response. By default, the deadline for a fetch
> > > > is 5 seconds. The maximum deadline is 60 seconds for HTTP requests and
> > > > 10 minutes for task queue and cron job requests.
>
> > > > Now, how can i set deadline to 60-sec ?
>
> > > > --
> > > > 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-appengi...@googlegroups.com .
> > > > To post to this group, send email to 
> > > > google-a...@googlegroups.com.
>
> > > > Visit this group athttp://
> > groups.google.com/group/google-appengine?hl=en.
> > > > For more options, visithttps://groups.google.com/groups/opt_out.
>
> > > --
> > > Dan Holevoet
> > > Google Developer Relations

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] can I deploy any war file to GAE

[Eman Hossny]

many thanks for ur reply.
I understood from ur reply that it is possible to deploy war file to GAE
through using CLI.--> is what true? if yes, I hope to create an application
that can be used to deploy any war file to GAE. so I asked if there exists
any library which i can use in my app to deploy war file to GAE??

On Sat, Jun 1, 2013 at 5:23 PM, Ludovic Champenois  wrote:

> On 5/31/13 6:27 PM, e.hos...@fci-cu.edu.eg wrote:
>
>> Hello All,
>>If I have a dynamic web project which is finally represented as a war
>> file. Can I deploy this war file to GAE? or should I refactor my project
>> again to be implemented as a new Web application using Google button in the
>> Eclipse toolbar?
>>
>
> Eclipse Dynamic Web Project support is coming. Meanwhile you'll have to
> 'export as a war' this project and use the regular app engine cli tooling
> to do the remote deployment.
> Ludo
>
>  --
>> 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+unsubscribe@**googlegroups.com
>> .
>>
>> To post to this group, send email to 
>> google-appengine@googlegroups.**com
>> .
>> Visit this group at http://groups.google.com/**
>> group/google-appengine?hl=en
>> .
>> For more options, visit 
>> https://groups.google.com/**groups/opt_out
>> .
>>
>>
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/**
> topic/google-appengine/**c5M4xvgNc5o/unsubscribe?hl=en
> .
> To unsubscribe from this group and all its topics, send an email to
> google-appengine+unsubscribe@**googlegroups.com
> .
> To post to this group, send email to 
> google-appengine@googlegroups.**com
> .
> Visit this group at http://groups.google.com/**
> group/google-appengine?hl=en
> .
> For more options, visit 
> https://groups.google.com/**groups/opt_out
> .
>
>
>


-- 
Eman Hossny,
Teacher Assistant,
Computer Science Department,
Faculty of Computers and Information
Cairo University, Egypt

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] App Engine console really slow lately?

[Jason Collins]

Has anyone else found the App Engine dashboard/console really, really slow 
lately (perhaps the past week)?

It's painful to use for me.

j

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: App Engine console really slow lately?

[Jason Collins]

Oh - and lots of errors too:

Server Error

A server error has occurred.

Return to Applications screen » 

On Tuesday, 4 June 2013 08:22:27 UTC-6, Jason Collins wrote:
>
> Has anyone else found the App Engine dashboard/console really, really slow 
> lately (perhaps the past week)?
>
> It's painful to use for me.
>
> j
>

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] Re: Memcache expiration

[Vinny P]

On Monday, June 3, 2013 9:18:14 AM UTC-5, Pertti Kellomäki wrote:

> In my case the memcache entry reflects what would be the result of a 
> particular datastore query, so if the entry is purged the datastore query 
> can always be run.
>
>
That is exactly the recommended best practice way to use the memcache + 
datastore, so your implementation is great!

-
-Vinny P
Technology & Media Advisor
Chicago, IL

My Go side project: http://invalidmail.com/

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] Re: Memcache expiration

[Pertti Kellomäki]

Glad to hear that ;-)

Pertti


On Tue, Jun 4, 2013 at 5:55 PM, Vinny P  wrote:

> On Monday, June 3, 2013 9:18:14 AM UTC-5, Pertti Kellomäki wrote:
>
>> In my case the memcache entry reflects what would be the result of a
>> particular datastore query, so if the entry is purged the datastore query
>> can always be run.
>>
>>
> That is exactly the recommended best practice way to use the memcache +
> datastore, so your implementation is great!
>
> -
> -Vinny P
> Technology & Media Advisor
> Chicago, IL
>
> My Go side project: http://invalidmail.com/
>
>  --
> 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 http://groups.google.com/group/google-appengine?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] Re: Some questions about instances

[Barry Hunter]

Dont forget Go. (and ultimately PHP :)

By all accounts Go fares really well on AppEngine. And offers built in
concurrency.


On Tue, Jun 4, 2013 at 7:02 AM, timh  wrote:

> Which is better is subjective.  I prefer python, others java.  Things to
> consider how much existing code from other sources for python or java that
> already run on appengine are you likely to use. That would feature highly
> in your decision making process.  Performance with java seems to depend on
> startup times and how big/heavy your stack is.  Big heavy python stacks
> that do a lot at startup on appengine can have startup time problems too.
>
>
> On Tuesday, June 4, 2013 12:10:49 AM UTC+8, Sebastián Benítez wrote:
>>
>> Hi there. I'm looking to create an Android/iOS (perhaps web too) social
>> application and I'm considering GAE as backend.
>>
>> For what I could gather, a single frontend instance is launched when a
>> request arrives. Is that instance also used (as in multiple threads) to
>> serve other incoming concurrent requests or other instances are launched?
>>
>> What are the benefits of using Java/Python. I'm thinking the case of the
>> app being eventually successfull and needing to handle 1M/10M users. I
>> would asume Java is a better fit, but considering what I've read lately
>> about launch performance, I'm not so sure now.
>>
>> Thank you.
>>
>  --
> 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 http://groups.google.com/group/google-appengine?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] get user by access token

[Jozef Môstka]

Hi all.

I need login user in server side by access token and get their user 
infomrmations. it is possible ? Im looks in com.google.appengine.api but Im 
not find it.
I get acces token in client side using google oauth2 and after send to 
server.


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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] UnicodeEncodeError but still saves to the Datastore

[Renzo Nuccitelli]

What i do in my application is setting unicode literals in my scripts. All 
of them start with:

from __future__ import unicode_literals

Once GAE and Jinja, my template system, work just fine with this 
configuration, i have no hadaches with strings.

 Good Lucky,
 Renzo

On Monday, June 3, 2013 3:08:42 PM UTC-3, Takashi Matsuo (Google) wrote:
>
>
>
>
> On Sun, Jun 2, 2013 at 4:18 PM, NP >wrote:
>
>> Hello all,
>>
>> My datastore model has an attribute of class string. According to the 
>> documentation, the String class should be of type str or unicode.
>>
>> The data I'm trying to save is unicode (I confirmed this by printing out 
>> the type and the original page was encoded in utf-8).
>>
>> My data is successfully saved to the datastore but it still raises the 
>> following exception 'ascii' codec can't encode character u'\u2019' in 
>> position 6: ordinal not in range(128)
>>
>
> When does this exception happen? From the error message, you're trying to 
> encode u'\u2019' (RIGHT SINGLE QUOTATION MARK) with the 'ascii' codec. Here 
> is an example:
>
> >>> u = u'\u2019'
> >>> u.encode('ascii')
> Traceback (most recent call last):
>   File "", line 1, in 
> UnicodeEncodeError: 'ascii' codec can't encode character u'\u2019' in 
> position 0: ordinal not in range(128)
> >>> u.encode('utf-8') # you can get an utf-8 encoded binary string
> '\xe2\x80\x99'
>  
>
>>
>> I'm curious as to why an exception is being raised even though the data 
>> is unicode and why even with the exception, the data is still saved 
>> successfully.
>>
>> Apart from specifically trapping this error using something like 
>> {exception UnicodeEncodeError: pass}, is there a way to prevent this error?
>>
>
> I don't recommend doing that. I recommend you check where the exception 
> occurs and fix it.
>
> -- Takashi
>  
>
>>
>>  
>>
>> -- 
>> 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-appengi...@googlegroups.com .
>> To post to this group, send email to 
>> google-a...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/google-appengine?hl=en
>> .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>
>
>
> -- 
> Takashi Matsuo | Developers Programs Engineer | tma...@google.com
>  

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Task Queues not running

[Scott]

My application isn't running tasks in the task queue right now. It hasn't 
been for four hours. I get errors on the dashboard when I try to view 
specific queues (sometimes) or when I try to manually run a task (all the 
time it seems). Is anyone else having this problem? These tasks really need 
to run so I'd appreciate a response from Google about this.

My application id is write-way.

Hurry.

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] 1.8.1 Pre-release SDKs Available.

[Richmond Manzana]

Hello Again Everyone!

We've been busy since I/O!

Pre-release SDKs for Python and Java here:
http://code.google.com/p/**googleappengine/downloads/list

Please see the pre-release notes below.

Cheers,
Richmond Manzana


App Engine Python SDK - Pre-Release Notes

Version 1.8.1
===
- The Task Queue async API is now a GA feature. The asynchronous methods
  improve utilization by allowing your app to add, lease and delete multiple
  tasks in parallel.
- Cloud Console projects are now created by default whenever a new App 
Engine
  app is created.  This is a Preview feature.
- The Experimental Files API has been deprecated in favor of the Google 
Cloud
  Storage library, now available as a Preview feature.
- Bandwidth between App Engine and Google Cloud Storage is currently free of
  charge (this may change in the future for certain levels of service).
- The Search API has graduated from Experimental to Preview. Apps that have
  billing enabled can exceed the free quota levels and will be charged for
  usage above these levels.
- Estimated number of search results will only be accurate if <= the number 
of
  results requested. By default this can be overridden by setting
  number_found_accuracy QueryOption in the Search API.
- Dates, atoms, and number fields can now be found by searching without a 
field
  restriction in the Search API.
- A quoted empty string now returns atom fields with empty values for the
  Search API.
- Snippet and count functions are no longer allowed in sort expressions for 
the
  Search API.
- The Search API now has improved error messages for user errors and 
internal
  errors.
- The Datastore now assigns scattered auto ids by default. Legacy auto ids
  are still available via the 'auto_id_policy' option in app.yaml.
- The Sockets API now allows client code to call get/set options against
  sockets. Previously, calls raised "Not Implemented" exceptions. For 
supported
  options, calls to getsockopt will return a mock value and calls to 
setsockopt
  will be silently ignored.  Errors will continue to be raised for 
unsupported
  options. The currently supported options are: SO_KEEPALIVE, SO_DEBUG,
  TCP_NODELAY, SO_LINGER, SO_OOBINLINE, SO_SNDBUF, SO_RCVBUF, and 
SO_REUSEADDR.
- The ndb library now supports distinct queries. This is a Preview feature.
https://code.google.com/p/appengine-ndb-experiment/issues/detail?id=229


App Engine Java SDK - Pre-Release Notes

Version 1.8.1
=
- This SDK will be the last release that can deploy Java 6 apps. In 1.8.2,
  the SDK will only be compiled with the Java 7 compiler and the only target
  runtime will be Java 7.
- The Task Queue async API is now a GA feature. The asynchronous methods
  improve utilization by allowing your app to add, lease and delete multiple
  tasks in parallel.
- Cloud Console projects are now created by default whenever a new App 
Engine
  app is created.  This is a Preview feature.
- The Experimental Files API has been deprecated in favor of the Google 
Cloud
  Storage library, now available as a Preview feature.
- Bandwidth between App Engine and Google Cloud Storage is currently free of
  charge (this may change in the future for certain levels of service).
- The Search API has graduated from Experimental to Preview. Apps that have
  billing enabled can exceed the free quota levels and will be charged for
  usage above these levels.
- Estimated number of search results will only be accurate if <= the number 
of
  results requested. By default this can be overridden by setting X in the
  Search API.
- Dates, atoms, and number fields can now be found by searching without a 
field
  restriction in the Search API.
- A quoted empty string now returns atom fields with empty values for the
  Search API.
- Snippet and count functions are no longer allowed in sort expressions for 
the
  Search API.
- The Search API now has improved error messages for user errors and 
internal
  errors.
- The Datastore now assigns scattered auto ids by default. Legacy auto ids
  are still available via the 'auto_id_policy' option in appengine-web.xml.
- The Sockets API now allows client code to call get/set options against
  sockets. Previously, calls raised "Not Implemented" exceptions. When
  java.net.Socket.get() is called, a mock value is returned, calls 
to
  set() will be silently ignored.

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: How to set deadline for a PHP URL fetch?

[Vinny P]

Can you tell us what URL you're connecting to? The server may be slow or be 
difficult to resolve.

I would suggest using *stream_get_meta_data* ( 
http://us3.php.net/stream_get_meta_data ) to inspect the stream and see 
what exactly is going on - you'll get a more detailed error message.

-
-Vinny P
Technology & Media Advisor
Chicago, IL

My Go side project: http://invalidmail.com/

On Tuesday, June 4, 2013 6:51:47 AM UTC-5, 1moretime wrote:
>
> Hi, Stuart 
> Thanks for your reply, 
> I tried following code, but failed. 
>
>  
> $data = http_build_query($data); 
> $context = 
> array("http"=> 
>   array( 
> "method" => "POST", 
> "content" => $data, 
> //"header" => "Connection: keep-alive\r\n", 
> //"deadline" => 60, // The deadline can be up to a maximum 
> of 60 seconds for request handlers 
> "timeout" => 30 // GAE requests have a 30-second deadline 
>   ) 
> ); 
> $context = stream_context_create($context); 
>
> $result = file_get_contents($url, false, $context); 
>
>  
>
>
> Still got same warning message in gae logs. 
>
>  
>
> PHP Warning:  file_get_contents(..): failed to open 
> stream: Request deadline exceeded in /base/data/home/apps/.php 
> on line 93 
>
>  
>
>
> Any suggestion? 
>
>
>
> On Jun 4, 5:56 pm, Stuart Langley  wrote: 
> > set the timeout value in the http context to the number of seconds you 
> want 
> > the deadline to be. 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > On Tuesday, 4 June 2013 12:05:29 UTC+10, 1moretime wrote: 
> > 
> > > Thanks, Dan 
> > 
> > > I read that doc but PHP version not found. 
> > > would you pls give some php code? 
> > 
> > > On Jun 4, 4:16 am, Dan Holevoet  wrote: 
> > > > This is a great question for the App Engine Stack Overflow 
> > > > tag, 
> > > > which also conveniently happens to have an 
> > > > answer< 
> > >http://stackoverflow.com/questions/2162115/how-to-set-timeout-for-url...>for
> > > 
>
> > 
> > > > you! 
> > 
> > > > Thanks, 
> > > > Dan 
> > 
> > > > On Mon, Jun 3, 2013 at 8:20 AM, 1moretime  
> > > wrote: 
> > > > > URL Fetch overview says: 
> > 
> > > > > You can set a deadline for a request, the most amount of time the 
> > > > > service will wait for a response. By default, the deadline for a 
> fetch 
> > > > > is 5 seconds. The maximum deadline is 60 seconds for HTTP requests 
> and 
> > > > > 10 minutes for task queue and cron job requests. 
> > 
> > > > > Now, how can i set deadline to 60-sec ? 
> > 
> > > > > -- 
> > > > > 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-appengi...@googlegroups.com . 
> > > > > To post to this group, send email to 
> > > > > google-a...@googlegroups.com. 
>
> > 
> > > > > Visit this group athttp:// 
> > > groups.google.com/group/google-appengine?hl=en. 
> > > > > For more options, visithttps://groups.google.com/groups/opt_out. 
> > 
> > > > -- 
> > > > Dan Holevoet 
> > > > Google Developer Relations 
>

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: 1.8.1 Pre-release SDKs Available.

[Bryce Cutt]

Regarding the Files API deprecation:

Is this as of right now or as of the final release of SDK 1.8.1?

I guess files already written will continue to work as is since they are no 
different than other blobstore files? Anything wrong with that assumption?

With this announcement, Google's push for use of Cloud Storage, and the 
lack of a blobstore API in the PHP runtime should we be ready for you guys 
to announce the deprecation of the blobstore entirely? I hope not. I like 
the blobstore and how it is nicely and automatically isolated to a single 
app.

- Bryce


On Tuesday, June 4, 2013 11:46:22 AM UTC-7, Richmond Manzana wrote:
>
> Hello Again Everyone!
>
> We've been busy since I/O!
>
> Pre-release SDKs for Python and Java here:
> http://code.google.com/p/**googleappengine/downloads/list
>
> Please see the pre-release notes below.
>
> Cheers,
> Richmond Manzana
>
>
> App Engine Python SDK - Pre-Release Notes
>
> Version 1.8.1
> ===
> - The Task Queue async API is now a GA feature. The asynchronous methods
>   improve utilization by allowing your app to add, lease and delete 
> multiple
>   tasks in parallel.
> - Cloud Console projects are now created by default whenever a new App 
> Engine
>   app is created.  This is a Preview feature.
> - The Experimental Files API has been deprecated in favor of the Google 
> Cloud
>   Storage library, now available as a Preview feature.
> - Bandwidth between App Engine and Google Cloud Storage is currently free 
> of
>   charge (this may change in the future for certain levels of service).
> - The Search API has graduated from Experimental to Preview. Apps that have
>   billing enabled can exceed the free quota levels and will be charged for
>   usage above these levels.
> - Estimated number of search results will only be accurate if <= the 
> number of
>   results requested. By default this can be overridden by setting
>   number_found_accuracy QueryOption in the Search API.
> - Dates, atoms, and number fields can now be found by searching without a 
> field
>   restriction in the Search API.
> - A quoted empty string now returns atom fields with empty values for the
>   Search API.
> - Snippet and count functions are no longer allowed in sort expressions 
> for the
>   Search API.
> - The Search API now has improved error messages for user errors and 
> internal
>   errors.
> - The Datastore now assigns scattered auto ids by default. Legacy auto ids
>   are still available via the 'auto_id_policy' option in app.yaml.
> - The Sockets API now allows client code to call get/set options against
>   sockets. Previously, calls raised "Not Implemented" exceptions. For 
> supported
>   options, calls to getsockopt will return a mock value and calls to 
> setsockopt
>   will be silently ignored.  Errors will continue to be raised for 
> unsupported
>   options. The currently supported options are: SO_KEEPALIVE, SO_DEBUG,
>   TCP_NODELAY, SO_LINGER, SO_OOBINLINE, SO_SNDBUF, SO_RCVBUF, and 
> SO_REUSEADDR.
> - The ndb library now supports distinct queries. This is a Preview feature.
> 
> https://code.google.com/p/appengine-ndb-experiment/issues/detail?id=229
>
>
> App Engine Java SDK - Pre-Release Notes
>
> Version 1.8.1
> =
> - This SDK will be the last release that can deploy Java 6 apps. In 1.8.2,
>   the SDK will only be compiled with the Java 7 compiler and the only 
> target
>   runtime will be Java 7.
> - The Task Queue async API is now a GA feature. The asynchronous methods
>   improve utilization by allowing your app to add, lease and delete 
> multiple
>   tasks in parallel.
> - Cloud Console projects are now created by default whenever a new App 
> Engine
>   app is created.  This is a Preview feature.
> - The Experimental Files API has been deprecated in favor of the Google 
> Cloud
>   Storage library, now available as a Preview feature.
> - Bandwidth between App Engine and Google Cloud Storage is currently free 
> of
>   charge (this may change in the future for certain levels of service).
> - The Search API has graduated from Experimental to Preview. Apps that have
>   billing enabled can exceed the free quota levels and will be charged for
>   usage above these levels.
> - Estimated number of search results will only be accurate if <= the 
> number of
>   results requested. By default this can be overridden by setting X in the
>   Search API.
> - Dates, atoms, and number fields can now be found by searching without a 
> field
>   restriction in the Search API.
> - A quoted empty string now returns atom fields with empty values for the
>   Search API.
> - Snippet and count functions are no longer allowed in sort expressions 
> for the
>   Search API.
> - The Search API now has improved error messages for user errors and 
> internal
>   errors.
> - The Datastore now assigns scattered auto ids by default. Legacy auto ids
>   are still available via the 'auto_id

[google-appengine] Re: get user by access token

[Vinny P]

On Tuesday, June 4, 2013 10:48:26 AM UTC-5, Jozef Môstka wrote:

>
> I need login user in server side by access token and get their user 
> infomrmations. it is possible ? Im looks in com.google.appengine.api but Im 
> not find it.
>
>
What user information do you want? If you just need to authorize & grab 
their email address, you can use the Users service: 
https://developers.google.com/appengine/docs/java/users/overview 

If you want their user credentials for another API (such as YouTube) you 
need to do a separate OAuth process.


-
-Vinny P
Technology & Media Advisor
Chicago, IL

My Go side project: http://invalidmail.com/

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: 1.8.1 Pre-release SDKs Available.

[Doug Anderson]

Could you please clarify this point?
- The Experimental Files API has been deprecated in favor of the Google 
Cloud
  Storage library, now available as a Preview feature.

Does this mean Blobstore writes are deprecated (I assume so)?
Does it also mean the current Cloud Storage "files" based API is being 
replaced with an API I have not yet seen?
In other words... 
https://developers.google.com/appengine/docs/python/googlestorage/functions - 
is this deprecated?


On Tuesday, June 4, 2013 2:46:22 PM UTC-4, Richmond Manzana wrote:
>
> Hello Again Everyone!
>
> We've been busy since I/O!
>
> Pre-release SDKs for Python and Java here:
> http://code.google.com/p/**googleappengine/downloads/list
>
> Please see the pre-release notes below.
>
> Cheers,
> Richmond Manzana
>
>
> App Engine Python SDK - Pre-Release Notes
>
> Version 1.8.1
> ===
> - The Task Queue async API is now a GA feature. The asynchronous methods
>   improve utilization by allowing your app to add, lease and delete 
> multiple
>   tasks in parallel.
> - Cloud Console projects are now created by default whenever a new App 
> Engine
>   app is created.  This is a Preview feature.
> - The Experimental Files API has been deprecated in favor of the Google 
> Cloud
>   Storage library, now available as a Preview feature.
> - Bandwidth between App Engine and Google Cloud Storage is currently free 
> of
>   charge (this may change in the future for certain levels of service).
> - The Search API has graduated from Experimental to Preview. Apps that have
>   billing enabled can exceed the free quota levels and will be charged for
>   usage above these levels.
> - Estimated number of search results will only be accurate if <= the 
> number of
>   results requested. By default this can be overridden by setting
>   number_found_accuracy QueryOption in the Search API.
> - Dates, atoms, and number fields can now be found by searching without a 
> field
>   restriction in the Search API.
> - A quoted empty string now returns atom fields with empty values for the
>   Search API.
> - Snippet and count functions are no longer allowed in sort expressions 
> for the
>   Search API.
> - The Search API now has improved error messages for user errors and 
> internal
>   errors.
> - The Datastore now assigns scattered auto ids by default. Legacy auto ids
>   are still available via the 'auto_id_policy' option in app.yaml.
> - The Sockets API now allows client code to call get/set options against
>   sockets. Previously, calls raised "Not Implemented" exceptions. For 
> supported
>   options, calls to getsockopt will return a mock value and calls to 
> setsockopt
>   will be silently ignored.  Errors will continue to be raised for 
> unsupported
>   options. The currently supported options are: SO_KEEPALIVE, SO_DEBUG,
>   TCP_NODELAY, SO_LINGER, SO_OOBINLINE, SO_SNDBUF, SO_RCVBUF, and 
> SO_REUSEADDR.
> - The ndb library now supports distinct queries. This is a Preview feature.
> 
> https://code.google.com/p/appengine-ndb-experiment/issues/detail?id=229
>
>
> App Engine Java SDK - Pre-Release Notes
>
> Version 1.8.1
> =
> - This SDK will be the last release that can deploy Java 6 apps. In 1.8.2,
>   the SDK will only be compiled with the Java 7 compiler and the only 
> target
>   runtime will be Java 7.
> - The Task Queue async API is now a GA feature. The asynchronous methods
>   improve utilization by allowing your app to add, lease and delete 
> multiple
>   tasks in parallel.
> - Cloud Console projects are now created by default whenever a new App 
> Engine
>   app is created.  This is a Preview feature.
> - The Experimental Files API has been deprecated in favor of the Google 
> Cloud
>   Storage library, now available as a Preview feature.
> - Bandwidth between App Engine and Google Cloud Storage is currently free 
> of
>   charge (this may change in the future for certain levels of service).
> - The Search API has graduated from Experimental to Preview. Apps that have
>   billing enabled can exceed the free quota levels and will be charged for
>   usage above these levels.
> - Estimated number of search results will only be accurate if <= the 
> number of
>   results requested. By default this can be overridden by setting X in the
>   Search API.
> - Dates, atoms, and number fields can now be found by searching without a 
> field
>   restriction in the Search API.
> - A quoted empty string now returns atom fields with empty values for the
>   Search API.
> - Snippet and count functions are no longer allowed in sort expressions 
> for the
>   Search API.
> - The Search API now has improved error messages for user errors and 
> internal
>   errors.
> - The Datastore now assigns scattered auto ids by default. Legacy auto ids
>   are still available via the 'auto_id_policy' option in appengine-web.xml.
> - The Sockets API now allows client code to call get/set options 

[google-appengine] Re: How can I delete my "Entity and Indexes" in my app engine home page?

[Vinny P]

On Monday, June 3, 2013 12:59:59 AM UTC-5, 武萌 wrote:
>
> I have deployed some useless "Entity and Indexes" for testing.
> Now I want to delete them.
> How can I do that?
>

Depends on the language for your app. If you have a Java application, you 
have a file marked datastore-indexes.xml in your /war/ directory. Open it 
up, and delete the XML lines that define your unwanted indexes. If you have 
a Python or Go app, the file will be called index.yaml and will have the 
same definitions in YAML format.

Once you've deleted the unwanted index definitions, you need to vacuum the 
indexes (delete them on App Engine Production). Execute the appcfg command 
here: 
https://developers.google.com/appengine/docs/python/tools/uploadinganapp#Deleting_Unused_Indexes
 (this 
operation may take some time, be patient). Remember to upload the edited 
copy of your app when you're done.

To delete entities, you can go into the datastore viewer and delete them, 
or programmatically delete them through the API.


-
-Vinny P
Technology & Media Advisor
Chicago, IL

My Go side project: http://invalidmail.com/

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: 1.8.1 Pre-release SDKs Available.

[Kaan Soral]

+1 on this question
I've been using blobstore for years, it's not so bad, it's bad but not too 
bad

Should I invest my time and switch to Cloud Storage? (I don't even know how 
it works, whether it's practical for image like files etc. since blobstore 
did the job I've never investigated it)

On Tuesday, June 4, 2013 11:45:35 PM UTC+3, Bryce Cutt wrote:
>
> Regarding the Files API deprecation:
>
> Is this as of right now or as of the final release of SDK 1.8.1?
>
> I guess files already written will continue to work as is since they are 
> no different than other blobstore files? Anything wrong with that 
> assumption?
>
> With this announcement, Google's push for use of Cloud Storage, and the 
> lack of a blobstore API in the PHP runtime should we be ready for you guys 
> to announce the deprecation of the blobstore entirely? I hope not. I like 
> the blobstore and how it is nicely and automatically isolated to a single 
> app.
>
> - Bryce
>
>
> On Tuesday, June 4, 2013 11:46:22 AM UTC-7, Richmond Manzana wrote:
>>
>> Hello Again Everyone!
>>
>> We've been busy since I/O!
>>
>> Pre-release SDKs for Python and Java here:
>> http://code.google.com/p/**googleappengine/downloads/list
>>
>> Please see the pre-release notes below.
>>
>> Cheers,
>> Richmond Manzana
>>
>>
>> App Engine Python SDK - Pre-Release Notes
>>
>> Version 1.8.1
>> ===
>> - The Task Queue async API is now a GA feature. The asynchronous methods
>>   improve utilization by allowing your app to add, lease and delete 
>> multiple
>>   tasks in parallel.
>> - Cloud Console projects are now created by default whenever a new App 
>> Engine
>>   app is created.  This is a Preview feature.
>> - The Experimental Files API has been deprecated in favor of the Google 
>> Cloud
>>   Storage library, now available as a Preview feature.
>> - Bandwidth between App Engine and Google Cloud Storage is currently free 
>> of
>>   charge (this may change in the future for certain levels of service).
>> - The Search API has graduated from Experimental to Preview. Apps that 
>> have
>>   billing enabled can exceed the free quota levels and will be charged for
>>   usage above these levels.
>> - Estimated number of search results will only be accurate if <= the 
>> number of
>>   results requested. By default this can be overridden by setting
>>   number_found_accuracy QueryOption in the Search API.
>> - Dates, atoms, and number fields can now be found by searching without a 
>> field
>>   restriction in the Search API.
>> - A quoted empty string now returns atom fields with empty values for the
>>   Search API.
>> - Snippet and count functions are no longer allowed in sort expressions 
>> for the
>>   Search API.
>> - The Search API now has improved error messages for user errors and 
>> internal
>>   errors.
>> - The Datastore now assigns scattered auto ids by default. Legacy auto ids
>>   are still available via the 'auto_id_policy' option in app.yaml.
>> - The Sockets API now allows client code to call get/set options against
>>   sockets. Previously, calls raised "Not Implemented" exceptions. For 
>> supported
>>   options, calls to getsockopt will return a mock value and calls to 
>> setsockopt
>>   will be silently ignored.  Errors will continue to be raised for 
>> unsupported
>>   options. The currently supported options are: SO_KEEPALIVE, SO_DEBUG,
>>   TCP_NODELAY, SO_LINGER, SO_OOBINLINE, SO_SNDBUF, SO_RCVBUF, and 
>> SO_REUSEADDR.
>> - The ndb library now supports distinct queries. This is a Preview 
>> feature.
>> 
>> https://code.google.com/p/appengine-ndb-experiment/issues/detail?id=229
>>
>>
>> App Engine Java SDK - Pre-Release Notes
>>
>> Version 1.8.1
>> =
>> - This SDK will be the last release that can deploy Java 6 apps. In 1.8.2,
>>   the SDK will only be compiled with the Java 7 compiler and the only 
>> target
>>   runtime will be Java 7.
>> - The Task Queue async API is now a GA feature. The asynchronous methods
>>   improve utilization by allowing your app to add, lease and delete 
>> multiple
>>   tasks in parallel.
>> - Cloud Console projects are now created by default whenever a new App 
>> Engine
>>   app is created.  This is a Preview feature.
>> - The Experimental Files API has been deprecated in favor of the Google 
>> Cloud
>>   Storage library, now available as a Preview feature.
>> - Bandwidth between App Engine and Google Cloud Storage is currently free 
>> of
>>   charge (this may change in the future for certain levels of service).
>> - The Search API has graduated from Experimental to Preview. Apps that 
>> have
>>   billing enabled can exceed the free quota levels and will be charged for
>>   usage above these levels.
>> - Estimated number of search results will only be accurate if <= the 
>> number of
>>   results requested. By default this can be overridden by setting X in the
>>   Search API.
>> - Dates, atoms, and number

[google-appengine] How do I create an App Engine application in the EU without a Premier account?

[Jon Ramvi]

It's stated in the documentation that it's possible:

If you have an App Engine Premier account, you can specify that your new 
application should reside in the European Union rather than the United 
States. For developers that do not have a Premier account, you will need to 
enable billing for applications that should reside in the European Union.
https://developers.google.com/appengine/docs/python/gettingstartedpython27/uploading

But you can't set up billing without creating the application first, and 
when the application is created you can't edit the location, so either 
isn't is possible for non-Premier accounts to create apps in the EU or I 
need a step by step guide on how to activate billing before creating the 
app.

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] JPA @PrePersist does not work on a child :(

[nermin . brgulja]

Hello Group,

I have a "probably simple" problem with my application which I am obviously 
not able to solve.

Two Classes: CompanyX, TradesmanX
CompanyX stays in a OneToOne Connection with TradesmanX

I use @PrePersist on Tradesman in order to pre-set some fields (e.g. Has 
password or set Account creation date) before the Object gets persisted in 
the DB.

My code is available here:
https://dl.dropboxusercontent.com/u/2983671/JPA_Problem/JPA_Problem.zip

@Entity
public class CompanyX {
...
@OneToOne(cascade=CascadeType.ALL)
private TradesmanX adminUser;
}


@Entity
public class TradesmanX {
...
@PrePersist
public void myMethod(){
System.out.println("Pre Persist");
this.setFirstName("USER_X");
}
...
}

//Here is how I persist them within my test servlet:

private void testPersistenceTwo() {

CompanyX company = new CompanyX();
company.setName("my Comp");

TradesmanX user = new TradesmanX();
user.setFirstName("Test_FName");
user.setLastName("Test_Lname");

company.setAdminUser(user);
company.persist();
}


The ERROR l am facing looks like follows:

javax.persistence.PersistenceException: Detected attempt to establish 
CompanyX(no-id-yet) as the parent of TradesmanX(7) but the entity 
identified by TradesmanX(7) has already been persisted without a parent.  A 
parent cannot be established or changed once an object has been persisted.
at 
org.datanucleus.api.jpa.NucleusJPAHelper.getJPAExceptionForNucleusException(NucleusJPAHelper.java:302)
at 
org.datanucleus.api.jpa.JPAEntityManager.close(JPAEntityManager.java:197)
at com.emajstor.server.persistence.CompanyX.persist(CompanyX.java:42)
at 
com.emajstor.server.test.MyTestServlet.testPersistenceTwo(MyTestServlet.java:88)
at com.emajstor.server.test.MyTestServlet.doGet(MyTestServlet.java:41)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at 
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
at 
com.google.appengine.api.socket.dev.DevSocketFilter.doFilter(DevSocketFilter.java:74)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
com.google.appengine.tools.development.ResponseRewriterFilter.doFilter(ResponseRewriterFilter.java:123)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
com.google.appengine.tools.development.HeaderVerificationFilter.doFilter(HeaderVerificationFilter.java:34)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java:63)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:43)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java:125)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
com.google.appengine.tools.development.DevAppServerServersFilter.doDirectRequest(DevAppServerServersFilter.java:369)
at 
com.google.appengine.tools.development.DevAppServerServersFilter.doDirectServerRequest(DevAppServerServersFilter.java:352)
at 
com.google.appengine.tools.development.DevAppServerServersFilter.doFilter(DevAppServerServersFilter.java:115)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
at 
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at 
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at 
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at 
com.google.appengine.tools.development.DevAppEngineWebAppContext.handle(DevAppEngineWebAppContext.java:97)
at 
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at 
com.google.appengine.tools.development.JettyContainerService$ApiProxyHandler.handle(JettyContainerService.java:438)
at 
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at 
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at 
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
at 

[google-appengine] Count datastore reads for request

[Yair Eshel]

I suspect one of my requests is taking more datastore calls then I set in 
my script. Any way to see datastore calls count, per request in my logs?

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Regarding the Backend development of my Android APP

[innernetab]

Hi,
I am a newbie to Google app engine and android app. As I have got a project 
with specifications has Google app engine needs to be used.
 Now my problem is I am unable to find the tutorial for creation of 
database or table on app engine and uploading of my Backend PHP or python 
code.

So can one please help me. 


-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] Count datastore reads for request

[Matt Jibson]

You can use appstats to do that:
https://developers.google.com/appengine/docs/python/tools/appstats

Sorry for the previous link, thought it was on the go list.


On Tue, Jun 4, 2013 at 11:08 AM, Yair Eshel  wrote:

> I suspect one of my requests is taking more datastore calls then I set in
> my script. Any way to see datastore calls count, per request in my logs?
>
> --
> 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 http://groups.google.com/group/google-appengine?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] Count datastore reads for request

[Matt Jibson]

http://godoc.org/github.com/mjibson/appstats


On Tue, Jun 4, 2013 at 11:08 AM, Yair Eshel  wrote:

> I suspect one of my requests is taking more datastore calls then I set in
> my script. Any way to see datastore calls count, per request in my logs?
>
> --
> 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 http://groups.google.com/group/google-appengine?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: Task Queues not running

[Diego]

Mines either.

On Tuesday, June 4, 2013 3:35:41 PM UTC-3, Scott wrote:
>
> My application isn't running tasks in the task queue right now. It hasn't 
> been for four hours. I get errors on the dashboard when I try to view 
> specific queues (sometimes) or when I try to manually run a task (all the 
> time it seems). Is anyone else having this problem? These tasks really need 
> to run so I'd appreciate a response from Google about this.
>
> My application id is write-way.
>
> Hurry.
>

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: 1.8.1 Pre-release SDKs Available.

[Max Ross]

Hi everyone,

I'll try to batch answers to multiple questions into a single response.

1) We're not making any Blobstore announcements or decisions in this 
release.

2) The only thing we're announcing here is our intent to decommission the 
experimental Files API. That's
https://developers.google.com/appengine/docs/python/googlestorage/functions 
and https://developers.google.com/appengine/docs/java/googlestorage/overview
We'll give you fair warning before we actually turn it down. We're 
announcing this now to give everyone who uses the Files API enough time to 
move over to the Google Cloud Storage client library, which we're launching 
in Preview mode.

3) We (very quietly) announced the availability of the Google Cloud Storage 
client library in a 
poston
 this forum back in January. There are full-fledged docs for this library 
coming out with the official 1.8.1 announcement, including a guide to 
migrating off the Files API.

I hope this helps.

Thanks,
Max

On Tuesday, June 4, 2013 2:13:19 PM UTC-7, Kaan Soral wrote:
>
> +1 on this question
> I've been using blobstore for years, it's not so bad, it's bad but not too 
> bad
>
> Should I invest my time and switch to Cloud Storage? (I don't even know 
> how it works, whether it's practical for image like files etc. since 
> blobstore did the job I've never investigated it)
>
> On Tuesday, June 4, 2013 11:45:35 PM UTC+3, Bryce Cutt wrote:
>>
>> Regarding the Files API deprecation:
>>
>> Is this as of right now or as of the final release of SDK 1.8.1?
>>
>> I guess files already written will continue to work as is since they are 
>> no different than other blobstore files? Anything wrong with that 
>> assumption?
>>
>> With this announcement, Google's push for use of Cloud Storage, and the 
>> lack of a blobstore API in the PHP runtime should we be ready for you guys 
>> to announce the deprecation of the blobstore entirely? I hope not. I like 
>> the blobstore and how it is nicely and automatically isolated to a single 
>> app.
>>
>> - Bryce
>>
>>
>> On Tuesday, June 4, 2013 11:46:22 AM UTC-7, Richmond Manzana wrote:
>>>
>>> Hello Again Everyone!
>>>
>>> We've been busy since I/O!
>>>
>>> Pre-release SDKs for Python and Java here:
>>> http://code.google.com/p/**googleappengine/downloads/list
>>>
>>> Please see the pre-release notes below.
>>>
>>> Cheers,
>>> Richmond Manzana
>>>
>>>
>>> App Engine Python SDK - Pre-Release Notes
>>>
>>> Version 1.8.1
>>> ===
>>> - The Task Queue async API is now a GA feature. The asynchronous methods
>>>   improve utilization by allowing your app to add, lease and delete 
>>> multiple
>>>   tasks in parallel.
>>> - Cloud Console projects are now created by default whenever a new App 
>>> Engine
>>>   app is created.  This is a Preview feature.
>>> - The Experimental Files API has been deprecated in favor of the Google 
>>> Cloud
>>>   Storage library, now available as a Preview feature.
>>> - Bandwidth between App Engine and Google Cloud Storage is currently 
>>> free of
>>>   charge (this may change in the future for certain levels of service).
>>> - The Search API has graduated from Experimental to Preview. Apps that 
>>> have
>>>   billing enabled can exceed the free quota levels and will be charged 
>>> for
>>>   usage above these levels.
>>> - Estimated number of search results will only be accurate if <= the 
>>> number of
>>>   results requested. By default this can be overridden by setting
>>>   number_found_accuracy QueryOption in the Search API.
>>> - Dates, atoms, and number fields can now be found by searching without 
>>> a field
>>>   restriction in the Search API.
>>> - A quoted empty string now returns atom fields with empty values for the
>>>   Search API.
>>> - Snippet and count functions are no longer allowed in sort expressions 
>>> for the
>>>   Search API.
>>> - The Search API now has improved error messages for user errors and 
>>> internal
>>>   errors.
>>> - The Datastore now assigns scattered auto ids by default. Legacy auto 
>>> ids
>>>   are still available via the 'auto_id_policy' option in app.yaml.
>>> - The Sockets API now allows client code to call get/set options against
>>>   sockets. Previously, calls raised "Not Implemented" exceptions. For 
>>> supported
>>>   options, calls to getsockopt will return a mock value and calls to 
>>> setsockopt
>>>   will be silently ignored.  Errors will continue to be raised for 
>>> unsupported
>>>   options. The currently supported options are: SO_KEEPALIVE, SO_DEBUG,
>>>   TCP_NODELAY, SO_LINGER, SO_OOBINLINE, SO_SNDBUF, SO_RCVBUF, and 
>>> SO_REUSEADDR.
>>> - The ndb library now supports distinct queries. This is a Preview 
>>> feature.
>>> 
>>> https://code.google.com/p/appengine-ndb-experiment/issues/detail?id=

[google-appengine] Re: How to set deadline for a PHP URL fetch?

[1moretime]

Thanks Vinny

I'm trying to POST data to http://cx.xaa.cc/checksn.asp with gae php.
It seems that my post request written in php closed in about 5
seconds,
so i guess my request deadline was not set properly.
GAE don't support fclose, so i don't know how to use
stream_get_meta_data.

Jason


On Jun 5, 2:52 am, Vinny P  wrote:
> Can you tell us what URL you're connecting to? The server may be slow or be
> difficult to resolve.
>
> I would suggest using *stream_get_meta_data* 
> (http://us3.php.net/stream_get_meta_data) to inspect the stream and see
> what exactly is going on - you'll get a more detailed error message.
>
> -
> -Vinny P
> Technology & Media Advisor
> Chicago, IL
>
> My Go side project:http://invalidmail.com/
>
>
>
>
>
>
>
> On Tuesday, June 4, 2013 6:51:47 AM UTC-5, 1moretime wrote:
>
> > Hi, Stuart
> > Thanks for your reply,
> > I tried following code, but failed.
>
> > 
> >     $data = http_build_query($data);
> >     $context =
> >         array("http"=>
> >           array(
> >             "method" => "POST",
> >             "content" => $data,
> >             //"header" => "Connection: keep-alive\r\n",
> >             //"deadline" => 60, // The deadline can be up to a maximum
> > of 60 seconds for request handlers
> >             "timeout" => 30 // GAE requests have a 30-second deadline
> >           )
> >         );
> >     $context = stream_context_create($context);
>
> >     $result = file_get_contents($url, false, $context);
>
> > 
>
> > Still got same warning message in gae logs.
>
> > 
>
> > PHP Warning:  file_get_contents(..): failed to open
> > stream: Request deadline exceeded in /base/data/home/apps/.php
> > on line 93
>
> > 
>
> > Any suggestion?
>
> > On Jun 4, 5:56 pm, Stuart Langley  wrote:
> > > set the timeout value in the http context to the number of seconds you
> > want
> > > the deadline to be.
>
> > > On Tuesday, 4 June 2013 12:05:29 UTC+10, 1moretime wrote:
>
> > > > Thanks, Dan
>
> > > > I read that doc but PHP version not found.
> > > > would you pls give some php code?
>
> > > > On Jun 4, 4:16 am, Dan Holevoet  wrote:
> > > > > This is a great question for the App Engine Stack Overflow
> > > > > tag,
> > > > > which also conveniently happens to have an
> > > > > answer<
> > > >http://stackoverflow.com/questions/2162115/how-to-set-timeout-for-url...>for
>
> > > > > you!
>
> > > > > Thanks,
> > > > > Dan
>
> > > > > On Mon, Jun 3, 2013 at 8:20 AM, 1moretime 
> > > > wrote:
> > > > > > URL Fetch overview says:
>
> > > > > > You can set a deadline for a request, the most amount of time the
> > > > > > service will wait for a response. By default, the deadline for a
> > fetch
> > > > > > is 5 seconds. The maximum deadline is 60 seconds for HTTP requests
> > and
> > > > > > 10 minutes for task queue and cron job requests.
>
> > > > > > Now, how can i set deadline to 60-sec ?
>
> > > > > > --
> > > > > > 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-appengi...@googlegroups.com .
> > > > > > To post to this group, send email to 
> > > > > > google-a...@googlegroups.com.
>
> > > > > > Visit this group athttp://
> > > > groups.google.com/group/google-appengine?hl=en.
> > > > > > For more options, visithttps://groups.google.com/groups/opt_out.
>
> > > > > --
> > > > > Dan Holevoet
> > > > > Google Developer Relations

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: 1.8.1 Pre-release SDKs Available.

[Bryce Cutt]

So, so I don't misunderstand, when you say "experimental Files API" you are 
not including this one?
https://developers.google.com/appengine/docs/python/blobstore/blobstorefiles

That is the one I thought was being deprecated when I saw the announcement.

- Bryce


On Tuesday, June 4, 2013 5:07:59 PM UTC-7, Max Ross wrote:
>
> Hi everyone,
>
> I'll try to batch answers to multiple questions into a single response.
>
> 1) We're not making any Blobstore announcements or decisions in this 
> release.
>
> 2) The only thing we're announcing here is our intent to decommission the 
> experimental Files API. That's
> https://developers.google.com/appengine/docs/python/googlestorage/functionsand
>  
> https://developers.google.com/appengine/docs/java/googlestorage/overview
> We'll give you fair warning before we actually turn it down. We're 
> announcing this now to give everyone who uses the Files API enough time to 
> move over to the Google Cloud Storage client library, which we're launching 
> in Preview mode.
>
> 3) We (very quietly) announced the availability of the Google Cloud 
> Storage client library in a 
> poston
>  this forum back in January. There are full-fledged docs for this library 
> coming out with the official 1.8.1 announcement, including a guide to 
> migrating off the Files API.
>
> I hope this helps.
>
> Thanks,
> Max
>
> On Tuesday, June 4, 2013 2:13:19 PM UTC-7, Kaan Soral wrote:
>>
>> +1 on this question
>> I've been using blobstore for years, it's not so bad, it's bad but not 
>> too bad
>>
>> Should I invest my time and switch to Cloud Storage? (I don't even know 
>> how it works, whether it's practical for image like files etc. since 
>> blobstore did the job I've never investigated it)
>>
>> On Tuesday, June 4, 2013 11:45:35 PM UTC+3, Bryce Cutt wrote:
>>>
>>> Regarding the Files API deprecation:
>>>
>>> Is this as of right now or as of the final release of SDK 1.8.1?
>>>
>>> I guess files already written will continue to work as is since they are 
>>> no different than other blobstore files? Anything wrong with that 
>>> assumption?
>>>
>>> With this announcement, Google's push for use of Cloud Storage, and the 
>>> lack of a blobstore API in the PHP runtime should we be ready for you guys 
>>> to announce the deprecation of the blobstore entirely? I hope not. I like 
>>> the blobstore and how it is nicely and automatically isolated to a single 
>>> app.
>>>
>>> - Bryce
>>>
>>>
>>> On Tuesday, June 4, 2013 11:46:22 AM UTC-7, Richmond Manzana wrote:

 Hello Again Everyone!

 We've been busy since I/O!

 Pre-release SDKs for Python and Java here:
 http://code.google.com/p/**googleappengine/downloads/list

 Please see the pre-release notes below.

 Cheers,
 Richmond Manzana


 App Engine Python SDK - Pre-Release Notes

 Version 1.8.1
 ===
 - The Task Queue async API is now a GA feature. The asynchronous methods
   improve utilization by allowing your app to add, lease and delete 
 multiple
   tasks in parallel.
 - Cloud Console projects are now created by default whenever a new App 
 Engine
   app is created.  This is a Preview feature.
 - The Experimental Files API has been deprecated in favor of the Google 
 Cloud
   Storage library, now available as a Preview feature.
 - Bandwidth between App Engine and Google Cloud Storage is currently 
 free of
   charge (this may change in the future for certain levels of service).
 - The Search API has graduated from Experimental to Preview. Apps that 
 have
   billing enabled can exceed the free quota levels and will be charged 
 for
   usage above these levels.
 - Estimated number of search results will only be accurate if <= the 
 number of
   results requested. By default this can be overridden by setting
   number_found_accuracy QueryOption in the Search API.
 - Dates, atoms, and number fields can now be found by searching without 
 a field
   restriction in the Search API.
 - A quoted empty string now returns atom fields with empty values for 
 the
   Search API.
 - Snippet and count functions are no longer allowed in sort expressions 
 for the
   Search API.
 - The Search API now has improved error messages for user errors and 
 internal
   errors.
 - The Datastore now assigns scattered auto ids by default. Legacy auto 
 ids
   are still available via the 'auto_id_policy' option in app.yaml.
 - The Sockets API now allows client code to call get/set options against
   sockets. Previously, calls raised "Not Implemented" exceptions. For 
 supported
   options, calls to getsockopt 

Re: [google-appengine] Re: 1.8.1 Pre-release SDKs Available.

[Jason Galea]

yeh, same here, but it looks like they should have said "experimental Cloud
Files API"..
https://developers.google.com/appengine/docs/python/googlestorage/functions


On Wed, Jun 5, 2013 at 11:27 AM, Bryce Cutt  wrote:

> So, so I don't misunderstand, when you say "experimental Files API" you
> are not including this one?
>
> https://developers.google.com/appengine/docs/python/blobstore/blobstorefiles
>
> That is the one I thought was being deprecated when I saw the announcement
> .
>
> - Bryce
>
>
> On Tuesday, June 4, 2013 5:07:59 PM UTC-7, Max Ross wrote:
>>
>> Hi everyone,
>>
>> I'll try to batch answers to multiple questions into a single response.
>>
>> 1) We're not making any Blobstore announcements or decisions in this
>> release.
>>
>> 2) The only thing we're announcing here is our intent to decommission the
>> experimental Files API. That's
>> https://developers.google.com/**appengine/docs/python/**
>> googlestorage/functionsand
>> https://developers.google.**com/appengine/docs/java/**
>> googlestorage/overview
>> We'll give you fair warning before we actually turn it down. We're
>> announcing this now to give everyone who uses the Files API enough time to
>> move over to the Google Cloud Storage client library, which we're launching
>> in Preview mode.
>>
>> 3) We (very quietly) announced the availability of the Google Cloud
>> Storage client library in a 
>> poston
>>  this forum back in January. There are full-fledged docs for this library
>> coming out with the official 1.8.1 announcement, including a guide to
>> migrating off the Files API.
>>
>> I hope this helps.
>>
>> Thanks,
>> Max
>>
>> On Tuesday, June 4, 2013 2:13:19 PM UTC-7, Kaan Soral wrote:
>>>
>>> +1 on this question
>>> I've been using blobstore for years, it's not so bad, it's bad but not
>>> too bad
>>>
>>> Should I invest my time and switch to Cloud Storage? (I don't even know
>>> how it works, whether it's practical for image like files etc. since
>>> blobstore did the job I've never investigated it)
>>>
>>> On Tuesday, June 4, 2013 11:45:35 PM UTC+3, Bryce Cutt wrote:

 Regarding the Files API deprecation:

 Is this as of right now or as of the final release of SDK 1.8.1?

 I guess files already written will continue to work as is since they
 are no different than other blobstore files? Anything wrong with that
 assumption?

 With this announcement, Google's push for use of Cloud Storage, and the
 lack of a blobstore API in the PHP runtime should we be ready for you guys
 to announce the deprecation of the blobstore entirely? I hope not. I like
 the blobstore and how it is nicely and automatically isolated to a single
 app.

 - Bryce


 On Tuesday, June 4, 2013 11:46:22 AM UTC-7, Richmond Manzana wrote:
>
> Hello Again Everyone!
>
> We've been busy since I/O!
>
> Pre-release SDKs for Python and Java here:
> http://code.google.com/p/**googl**eappengine/downloads/list
>
> Please see the pre-release notes below.
>
> Cheers,
> Richmond Manzana
>
>
> App Engine Python SDK - Pre-Release Notes
>
> Version 1.8.1
> ==**=
> - The Task Queue async API is now a GA feature. The asynchronous
> methods
>   improve utilization by allowing your app to add, lease and delete
> multiple
>   tasks in parallel.
> - Cloud Console projects are now created by default whenever a new App
> Engine
>   app is created.  This is a Preview feature.
> - The Experimental Files API has been deprecated in favor of the
> Google Cloud
>   Storage library, now available as a Preview feature.
> - Bandwidth between App Engine and Google Cloud Storage is currently
> free of
>   charge (this may change in the future for certain levels of service).
> - The Search API has graduated from Experimental to Preview. Apps that
> have
>   billing enabled can exceed the free quota levels and will be charged
> for
>   usage above these levels.
> - Estimated number of search results will only be accurate if <= the
> number of
>   results requested. By default this can be overridden by setting
>   number_found_accuracy QueryOption in the Search API.
> - Dates, atoms, and number fields can now be found by searching
> without a field
>   restriction in the Search API.
> - A quoted empty string now returns atom fields with empty values for
> the
>   Search API.
> - Snippet and count functions are no longer allowed in sort
> expressions f

Re: [google-appengine] Regarding the Backend development of my Android APP

[Google Tasks Backup Moderator]

Try these

https://developers.google.com/appengine/docs/python/gettingstartedpython27/

https://developers.google.com/appengine/docs/python/gettingstartedpython27/usingdatastore

PHP link on the left side at https://developers.google.com/appengine/



On 4 June 2013 18:18,  wrote:

> Hi,
> I am a newbie to Google app engine and android app. As I have got a
> project with specifications has Google app engine needs to be used.
>  Now my problem is I am unable to find the tutorial for creation of
> database or table on app engine and uploading of my Backend PHP or python
> code.
>
> So can one please help me.
>
>
>  --
> 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 http://groups.google.com/group/google-appengine?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] Re: 1.8.1 Pre-release SDKs Available.

[Chris Ramsdale]

Jason, that is correct -- in a future release we are going to
decommission the Experimental Google Cloud Storage API Functions.  These
APIs and their Experimental status are documented at the following links:

   -
   https://developers.google.com/appengine/docs/python/googlestorage/functions
   -
   https://developers.google.com/appengine/docs/java/googlestorage/overview

Given this, we're moving the new Google Cloud Storage Client
Libraryto Preview in
the 1.8.1 release. Unlike Experimental features, Preview
features are guaranteed to move to General Availability (GA).  We encourage
developers to start moving over to the new Cloud Storage Client Library as
soon as possible.  Information on getting started can be found at the open
source project linked below.

https://code.google.com/p/appengine-gcs-client/

Cheers,

-- Chris Ramsdale

Product Manager, Google App Engine


On Tue, Jun 4, 2013 at 6:34 PM, Jason Galea  wrote:

> yeh, same here, but it looks like they should have said "experimental
> Cloud Files API"..
> https://developers.google.com/appengine/docs/python/googlestorage/functions
>
>
> On Wed, Jun 5, 2013 at 11:27 AM, Bryce Cutt  wrote:
>
>> So, so I don't misunderstand, when you say "experimental Files API" you
>> are not including this one?
>>
>> https://developers.google.com/appengine/docs/python/blobstore/blobstorefiles
>>
>> That is the one I thought was being deprecated when I saw the announcement
>> .
>>
>> - Bryce
>>
>>
>> On Tuesday, June 4, 2013 5:07:59 PM UTC-7, Max Ross wrote:
>>>
>>> Hi everyone,
>>>
>>> I'll try to batch answers to multiple questions into a single response.
>>>
>>> 1) We're not making any Blobstore announcements or decisions in this
>>> release.
>>>
>>> 2) The only thing we're announcing here is our intent to decommission
>>> the experimental Files API. That's
>>> https://developers.google.com/**appengine/docs/python/**
>>> googlestorage/functionsand
>>> https://developers.google.**com/appengine/docs/java/**
>>> googlestorage/overview
>>> We'll give you fair warning before we actually turn it down. We're
>>> announcing this now to give everyone who uses the Files API enough time to
>>> move over to the Google Cloud Storage client library, which we're launching
>>> in Preview mode.
>>>
>>> 3) We (very quietly) announced the availability of the Google Cloud
>>> Storage client library in a 
>>> poston
>>>  this forum back in January. There are full-fledged docs for this library
>>> coming out with the official 1.8.1 announcement, including a guide to
>>> migrating off the Files API.
>>>
>>> I hope this helps.
>>>
>>> Thanks,
>>> Max
>>>
>>> On Tuesday, June 4, 2013 2:13:19 PM UTC-7, Kaan Soral wrote:

 +1 on this question
 I've been using blobstore for years, it's not so bad, it's bad but not
 too bad

 Should I invest my time and switch to Cloud Storage? (I don't even know
 how it works, whether it's practical for image like files etc. since
 blobstore did the job I've never investigated it)

 On Tuesday, June 4, 2013 11:45:35 PM UTC+3, Bryce Cutt wrote:
>
> Regarding the Files API deprecation:
>
> Is this as of right now or as of the final release of SDK 1.8.1?
>
> I guess files already written will continue to work as is since they
> are no different than other blobstore files? Anything wrong with that
> assumption?
>
> With this announcement, Google's push for use of Cloud Storage, and
> the lack of a blobstore API in the PHP runtime should we be ready for you
> guys to announce the deprecation of the blobstore entirely? I hope not. I
> like the blobstore and how it is nicely and automatically isolated to a
> single app.
>
> - Bryce
>
>
> On Tuesday, June 4, 2013 11:46:22 AM UTC-7, Richmond Manzana wrote:
>>
>> Hello Again Everyone!
>>
>> We've been busy since I/O!
>>
>> Pre-release SDKs for Python and Java here:
>> http://code.google.com/p/**googl**eappengine/downloads/list
>>
>> Please see the pre-release notes below.
>>
>> Cheers,
>> Richmond Manzana
>>
>>
>> App Engine Python SDK - Pre-Release Notes
>>
>> Version 1.8.1
>> ==**=
>> - The Task Queue async API is now a GA feature. The asynchronous
>> methods
>>   improve utilization by allowing your app to add, lease and delete
>> multiple
>>   tasks in parallel.
>> - Cloud Console projects are now created by default whenever a new
>> App Engine
>>   app is created.  Thi

[google-appengine] Changed instance type from F1 to F4, need to restart app for change to take effect, how?

[Byron Gibson]

Hi all, 

GAE docs say that for GAE Java, if you change the instance type you must 
restart your app for the change to take effect.  But I'm missing the 
"Restart" button in the web control panel, and not finding the answer 
either here or at StackOverflow, or anywhere else.  How do you manually 
restart your GAE Java app?

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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: Changed instance type from F1 to F4, need to restart app for change to take effect, how?

[Byron Gibson]

Update:  seems to have auto-restarted a minute later.

On Tuesday, June 4, 2013 8:10:29 PM UTC-7, Byron Gibson wrote:
>
> Hi all, 
>
> GAE docs say that for GAE Java, if you change the instance type you must 
> restart your app for the change to take effect.  But I'm missing the 
> "Restart" button in the web control panel, and not finding the answer 
> either here or at StackOverflow, or anywhere else.  How do you manually 
> restart your GAE Java app?
>
> 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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: Wordpress + AppEngine = PressEngine

[@Mlaynes]

..really PHP is a language with quite a presence in the web development 
world .. and a lot of opensource projects very interesting like Wp, Elgg, 
Drupal, Magento and others, now they will can to run within GAE platform 
without major changes.. I think is a great news

@Mlaynes

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] working GAE-Java projects on Netbeans

[@Mlaynes]

to work GAE-Java Projects with Netbeans IDE until version 6.9 we had the 
support of kenai.com, but really worth noting that Kenai is no longer 
provided adequate support to their plugin and the updates constants of SDK 
for Java of Google App Engine, so several times we were looking for and 
reviewing several alternatives, and the most suitable we find is the 
following:

it's possible obtain a good plug-in for Netbeans 7.3 and GAE Java SDK 
v.1.8.x from this repository:
https://github.com/Valery-Sh/NbAppEngine

with this plug-in, GAE projects like guestbook sample or new personal 
projects are running very fine..

method of use:
1. delete completely App Engine server of your Netbeans (I had to reinstall 
Netbeans to remove the service completely, but there must be a way to do it)
2. download plug-in from : 
https://code.google.com/p/nb-gaelyk-plugin/downloads/detail?name=nbappengine-7.3-gae1.8.x.zip
 to 
any folder..
3. install plug-in : Tools / Plugins / Downloaded
4. verify update of plugins..
5. create a new server appengine with version 1.8.x of SDK for Java
6. create a new JavaWeb project for running on appengine server and/or 
testing guestbook sample.. 





my test about this : http://goo.gl/Vhz1k (language: es, with translate 
options)

best & happy coding !
@Mlaynes

http://mlaynessanchez.blogspot.com


-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.