Re: [google-appengine] Re: Upcoming changes to Task Queues

[DokiTops]

http://apps.facebook.com/godswar_online

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Upcoming changes to Task Queues

[DokiTops]

I also get this error enetering this app: Error: Server ErrorThe server 
encountered an error and could not complete your request.

If the problem persists, please 
report your 
problem and mention this error message and the query that caused it.

Then I end up here.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] everything is down

[Girish]

lol
by the way I recently made a game thats played between India and Pakistan
more here.. http://www.teampinch.com

On Mon, Feb 14, 2011 at 12:34 PM, Syed Ali Saim  wrote:

> We live in your neighbourhood aka Pakistan,
>
> and its working perfectly :), hurray hurray, just kidding
>
> I feel for you man, and updating google-appengine team :) know your work is
> appreciated in every corner of the world
>
>
>
>
> On Mon, Feb 14, 2011 at 11:46 AM, Girish  wrote:
>
>> I live in India and appspot and its applications seem to be down. System
>> status reports that everything is fine.
>> I cant even access my appspot account easily.
>>
>> This has happened many times in the last few days. anyone else
>> experiencing the same things?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google App Engine" group.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>



-- 
Regards

Girish Lakshminarayana
Technology Consultant & Director, Klea Global (http://www.kleaglobal.com/)
Mobile. +919871030744
Skype: anticlickwise
Twitter: http://www.twitter.com/anticlickwise
Blog: http://www.aboxtothinkoutof.com
*
*
*My Websites
*
http://www.trackthisnow.com
http://www.webtoim.com/site
http://www.dealzfull.com

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] everything is down

[Syed Ali Saim]

We live in your neighbourhood aka Pakistan,

and its working perfectly :), hurray hurray, just kidding

I feel for you man, and updating google-appengine team :) know your work is
appreciated in every corner of the world



On Mon, Feb 14, 2011 at 11:46 AM, Girish  wrote:

> I live in India and appspot and its applications seem to be down. System
> status reports that everything is fine.
> I cant even access my appspot account easily.
>
> This has happened many times in the last few days. anyone else experiencing
> the same things?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] everything is down

[Girish]

Thanks David

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] everything is down

[David Mora]

seems like there's something going on with the datastore:

http://code.google.com/status/appengine/detail/datastore/2011/02/13#ae-trust-detail-datastore-delete-latency
http://code.google.com/status/appengine/detail/datastore/2011/02/13#ae-trust-detail-datastore-update-latency
http://code.google.com/status/appengine/detail/datastore/2011/02/13#ae-trust-detail-datastore-put-latency

[delete, update, put: > 500 ms latency = probably apps are reaching
+1kms latency > unable to scale]

http://api-status.com/6404/117406/Google-App-Engine-API


On 14 February 2011 00:46, Girish  wrote:
> I live in India and appspot and its applications seem to be down. System
> status reports that everything is fine.
> I cant even access my appspot account easily.
> This has happened many times in the last few days. anyone else experiencing
> the same things?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>



-- 
http://about.me/david.mora

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] everything is down

[Devraj Mukherjee]

Accessible from Australia.

Have had no problems.

On Mon, Feb 14, 2011 at 5:46 PM, Girish  wrote:
> I live in India and appspot and its applications seem to be down. System
> status reports that everything is fine.
> I cant even access my appspot account easily.
> This has happened many times in the last few days. anyone else experiencing
> the same things?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] everything is down

[Girish]

I live in India and appspot and its applications seem to be down. System 
status reports that everything is fine. 
I cant even access my appspot account easily. 

This has happened many times in the last few days. anyone else experiencing 
the same things?

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] App Engine SDK 1.4.2 is out!

[Sandeep Koduri]

Thanks for the reply,

But tried to put in appconfig too. We have some custom developed filters for
django. these are invoked at the last in the call process.
Putting use_library  is showing this kind of errors

webapp.template.register_template_library('customfilters')
  File "C:\Program
Files\Google\google_appengine\google\appengine\ext\webapp\template.py",
line 269, in register_template_library
django.template.add_to_builtins(package_name)
  File "C:\Program
Files\Google\google_appengine\lib\django_1_2\django\template\__init__.py",
line 1049, in add_to_builtins
builtins.append(import_library(module))
  File "C:\Program
Files\Google\google_appengine\lib\django_1_2\django\template\__init__.py",
line 984, in import_library
app_path, taglib = taglib_module.rsplit('.',1)
ValueError: need more than 1 value to unpack


On Sun, Feb 13, 2011 at 10:43 PM, Geoffrey Spear wrote:

> Are you using appstats or some other middlewear that might be using
> webapp.template?  You need to call use_library() before any code tries to
> use django; app_config.py is probably a good place to put the call.
>
>
> On Sunday, February 13, 2011 10:44:38 AM UTC-5, $ÂÑЀ€P wrote:
>
>> Hi,
>>
>> tried to use use_library('django','1.2')
>>
>> This is giving this kind of error..., can any one help how to sort
>> this...
>>
>> E2011-02-13 07:08:52.561
>>
>> : django 
>> 1.2 was requested, but 0.96.4.None is already in use
>> Traceback (most recent call last):
>>   File 
>> "/base/data/home/apps/littleparadischool/1-2-36.348324395325175647/cricket/disxml.py",
>>  line 7, in 
>> use_library('django', '1.2')
>>   File 
>> "/base/python_runtime/python_lib/versions/1/google/appengine/dist/_library.py",
>>  line 291, in use_library
>> InstallLibrary(name, version, explicit=True)
>>   File 
>> "/base/python_runtime/python_lib/versions/1/google/appengine/dist/_library.py",
>>  line 250, in InstallLibrary
>> CheckInstalledVersion(name, version, explicit=True)
>>   File 
>> "/base/python_runtime/python_lib/versions/1/google/appengine/dist/_library.py",
>>  line 194, in CheckInstalledVersion
>> (name, desired_version, installed_version))
>>
>>
>> On Sun, Feb 13, 2011 at 6:01 AM, David Mora  wrote:
>>
>>> There seems to be a problem (in python) when using the bulk loader:
>>>
>>> UnacceptableVersionError: django 1.1 was requested, but 1.2.3.final.0
>>> is already in use
>>> [INFO] An error occurred. Shutting down...
>>>
>>> We load django 1.1 directly in app_config.py so it is used across all
>>> mapreduces/pipelines
>>>
>>> Would not say it is a issue yet since i have not properly debug it
>>> (hell, is weekend :) ) - if i found more info ill fill up a bug
>>> properly, thought i should share this, tho
>>>
>>> On 12 February 2011 14:30, Sandeep Koduri  wrote:
>>> > Thanks for the update, we were eager about this.
>>> > Thinking why the version release updates of python went after java
>>> ones,
>>> > different from regular process.
>>> > This version helps us lot
>>> >
>>> > On Sat, Feb 12, 2011 at 1:50 AM, Ikai Lan (Google)
>>> >  wrote:
>>> >>
>>> >> Hey everyone,
>>> >> The moment you've been waiting for is here. Drum roll please ... *drum
>>> >> roll* SDK 1.4.2 is out! I know you've all been anxious to get your
>>> hands on
>>> >> this release (many of you jumping the gun and download the SDK before
>>> the
>>> >> previous announcement). You won't be disappointed. Here's the official
>>> blog
>>> >> post:
>>> >>
>>> >>
>>> http://googleappengine.blogspot.com/2011/02/app-engine-142-sdk-api-updates-and.html
>>> >> One thing you'll notice is that Prospective Search (Matcher API) isn't
>>> in
>>> >> this release even though it was in the prerelease SDK. We're going to
>>> try to
>>> >> get it out for one of the upcoming releases. Apologies for those of
>>> you
>>> >> wanted to use it - it's coming soon, I promise!
>>> >> Release notes for 1.4.2 are below. As usual, you can update the SDK
>>> >> through all the standard means or via the downloads
>>> >> page: http://code.google.com/appengine/downloads.html
>>> >> Note: Some of you who downloaded the Java SDK prior to this
>>> announcement
>>> >> actually got a version that was missing the unit testing jars. If you
>>> >> downloaded the Java SDK over ~30 minutes ago and are wondering where
>>> all the
>>> >> testing jars went, please go ahead and download it again (if you
>>> didn't
>>> >> notice that the testing jars were missing ... well, shame on you, you
>>> should
>>> >> be writing unit tests).
>>> >> Java Version 1.4.2
>>> >> =
>>> >> - You can now vacuum datastore indexes with the Java SDK.
>>> >> - The XMPP API was updated to include presence and allow
>>> subscriptions.
>>> >> - The Task Queue now supports programmatic deleting of tasks.
>>> >> http://code.google.com/p/googleappengine/issues/detail?id=2588
>>> >> - The maximum rate per queue at which tasks are processed has been
>>> >> increased to
>>> >>   100 task per second.
>>> >>

Re: [google-appengine] Mobile Integration and the Channel API

[Nick Johnson (Google)]

Hi Richard,

The Channel API doesn't use websockets, as they're not widely deployed yet.
Instead, it (currently!) uses long-polling.

I'm not familiar with Phonegap or Titanium, but your best option is probably
to use existing push messaging solutions available on each device. Apple
provides a Push API, and Android has the Cloud To Device Messaging API.

-Nick Johnson

On Wed, Feb 9, 2011 at 11:54 AM, Richard Arrano wrote:

> Hello,
> I was thinking about how to integrate my App Engine app with mobile
> devices; my favorite choices so far are phonegap and Titanium, and it
> seems relatively simple to port things to these platforms. However,
> the sticking point has been that my application uses the Channel API.
> What I'm wondering is, what exactly does a mobile platform like
> phonegap or Titanium need to interface properly with the Channel API?
> I know WebSockets, but is there anything more than that? If anyone has
> any experience integrating their app with mobile devices and using
> Channel, I'd appreciate some ideas on how to do so. I realize this
> could be seen as a phonegap/Titanium question rather than an App
> Engine one but I'm particularly interested in what App Engine's JS is
> doing client-side so I can perhaps find some mobile platform specific
> hacks(for instance I've found some that enable WebSockets in
> phonegap). Any help is much appreciated.
>
> Thanks,
> Richard Arrano
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>


-- 
Nick Johnson, Developer Programs Engineer, App Engine
Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number:
368047

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Using the Channel API with a desktop app: possible?

[jonsm...@gmail.com]

On Sun, Feb 13, 2011 at 5:09 PM, Peter Petrov  wrote:
> This has the drawback that the user must have a Google Account in order to
> connect to GTalk. Unfortunately GTalk does not support e.g. SASL ANONYMOUS
> logins.

I'm wrestling with this same problem. Another solution is to allow
OAuth logins to a specific JID resource on Gtalk. Gtalk solves a lot
of my problems but there is no way to access with exposing a full
Google login.

Alternatively I could have them log into Twitter which supports OAuth.
But then I don't know a reliable way of sending directed Twitter
messages out from GAE.


> It would be perfect if the Channel API exposed directly its lower-level XMPP
> layer. Something like allowing the user to connect via XMPP as
> channel_id@app_id.appspotchannel.com using the channel_token as password.
>
> On Sun, Feb 13, 2011 at 11:26 PM, Michael Davidson 
> wrote:
>>
>> Another option would be to make an XMPP connection to Google Talk from
>> your app (there are XMPP libraries available for many languages), and
>> use the XMPP API to send messages to the client.
>>
>> Michael
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google App Engine" group.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>



-- 
Jon Smirl
jonsm...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Inviting another developer

[Michael Green]

I'm having trouble adding another developer to my application.  I invite 
them and they receive an e-mail.  However, when they click the e-mail it 
states that they are "Not authorized to access this application".  There is 
a second link in their invite that says they can login to their Google 
Account and accept the invitation that way.   When they login, there is no 
indication that there is a pending invite.  

Can somebody tell me what I'm missing?

Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: datastore

[Robert Kluin]

Start with the getting started guide:
  http://code.google.com/appengine/docs/python/gettingstarted/introduction.html


The Users API docs:
  http://code.google.com/appengine/docs/python/users/

And the datastore docs:
  http://code.google.com/appengine/docs/python/datastore/


Read those and try putting something together.


Robert





On Sun, Feb 13, 2011 at 17:00, Clinteney  wrote:
>  basically i am trying to use db.model to store the users information, i am
> just a beginner and dont know if that answers you question.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Blobstore file upload with other form values

[theone]

Thank you. I solved the problem. In my html form I forgot to put
enctype="multipart/form-data". It seems working now.

On Feb 13, 9:12 pm, Robert Kluin  wrote:
> Hi,
>   You're getting the IndexError because get_uploads is returning an
> empty list, which means there are no blob-info records for the 'file'
> field.
>
>   Your other error is because BlobstoreUploadHandler only allows
> redirects.  Like Doug suggests, you'll need to redirect to another
> page to output something.
>
> Robert
>
>
>
>
>
>
>
> On Sun, Feb 13, 2011 at 02:51, theone  wrote:
> > I don't need to return the values. My problem is that while I am able
> > to send file with a few form fields, It gives an error using many
> > fields:
> > w=upload_files[0]
> > IndexError: list index out of range
> > INFO     2011-02-13 07:43:10,884 dev_appserver_blobstore.py:328]
> > Upload handler returned 500
> > ERROR    2011-02-13 07:43:10,884 dev_appserver_blobstore.py:341]
> > Invalid upload handler response. Only 301, 302 and 303 statuses are
> > permitted and it may not have a content body.
> > INFO     2011-02-13 07:43:10,910 dev_appserver.py:3317] "POST /_ah/
> > upload/agZlcGN2ZGJyHAsSFV9fQmxvYlVwbG9hZFNlc3Npb25fXxjFAgw HTTP/1.1"
> > 500 -
>
> > In both cases I use the same definitions:
> > upload_files = self.get_uploads('file')
> > w=upload_files[0]
>
> > On Feb 13, 9:35 am, Doug Anderson  wrote:
> >> I have to retract my previous post... this does appear to be working
> >> for me.  I can use "self.request.get('description')" to retrieve the
> >> text description form field.  My previous problem was that
> >> name='descripton' was spelled wrong in my html form (missing the last
> >> 'i')... doh!
>
> >> I think your issue is that you lose your "self.response.out.write(N)"
> >> content when you redirect via "return self.redirect('/')"... that
> >> response body content won't survive the redirect (the redirect will
> >> provide its own content).  If you need to return the submitted N and S
> >> content then perhaps you could redirect to a URL that takes the 'a'
> >> object key as a parameter "self.redirect('/' +
> >> urllib.quote(a.key()))".  Of course you'd have to setup your handler
> >> to accept the parameter... but then you could re-retrieve 'a' object
> >> in the handler via a datastore get such as "a = db.get(a_key)"...
> >> assuming 'a_key' is the name of the parameter.
>
> >> On Feb 13, 1:54 am, theone  wrote:
>
> >> > I think you are right about BlobstoreUploadHandler limitations. When I
> >> > tried something like:
> >> > class X(db.Model):
> >> >     N = db.StringProperty()
> >> >     S = db.StringProperty()
> >> >     F = blobstore.BlobReferenceProperty()
>
> >> > class Upload(blobstore_handlers.BlobstoreUploadHandler):
> >> >     def post(self):
> >> >         upload_files = self.get_uploads('file')
> >> >         a=upload_files[0]
> >> >         N = self.request.get('name')
> >> >         S = self.request.get('sname')
> >> >         if S:
> >> >             m=N + S
> >> >         else:
> >> >             m=S + N
> >> >         self.response.out.write(N)
> >> >         self.response.out.write(S)
> >> >         a=X(N=m, S=S, F=a)
> >> >         a.put()
> >> >         return self.redirect('/')
>
> >> > It worked partly. I mean I put my model to datastore and file to
> >> > blobstore. However, it does not writes the thing like:
> >> > self.response.out.write(N). What I understand here we cannot use
> >> > everything in BlobstoreUploadHandler.
>
> >> > Also if you request the form fields, it does not work.
>
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Google App Engine" group.
> > To post to this group, send email to google-appengine@googlegroups.com.
> > To unsubscribe from this group, send email to 
> > google-appengine+unsubscr...@googlegroups.com.
> > For more options, visit this group 
> > athttp://groups.google.com/group/google-appengine?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] App Engine SDK 1.4.2 is out!

[Matt McDonald]

On Sun, Feb 13, 2011 at 12:13 PM, Geoffrey Spear wrote:

> Are you using appstats or some other middlewear that might be using
> webapp.template?  You need to call use_library() before any code tries to
> use django; app_config.py is probably a good place to put the call.


For clarity, that should be *appengine_config.py*
http://code.google.com/appengine/docs/python/tools/appstats.html#Configuring_Appstats


-- 
Matt McDonald

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: App Engine SDK 1.4.2 is out!

[Greg Darke]

Hi Colin,

You are not guaranteed a serialised ordering.

In the documentation
(http://code.google.com/appengine/docs/python/taskqueue/overview.html#Queue_Concepts)
it states "However, the system attempts to deliver the lowest latency
possible for any given task via specially optimized notifications to
the scheduler. Thus, in the case that a queue has a large backlog of
tasks, the system's scheduling may "jump" new tasks to the head of the
queue."

On 13 February 2011 02:54, Colin Hawkett  wrote:
> Thanks Ikai - great release! One question, can a queue that is rate limited
> to 1 concurrent task be seen as a FIFO serialised queue? i.e. is order
> guaranteed, even if the current running task fails it goes back to the front
> of the queue? I'm guessing you don't guarantee this behaviour but thought
> I'd check. Would be an excellent feature. Cheers,
> Colin
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>



-- 
Greg Darke

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Memcache problems

[James Broberg]

It was a dumb missing jar error, nothing to see here.

On 11 February 2011 19:33, James Broberg  wrote:
> Hi folks,
>
> Just set up a new dev environment on Linux with an existing codebase
> of mine and came across an odd error I hadn't encountered before.
>
> Has anyone seen the below error? I'm fairly certain memcache is the
> problem, not appstats, as I get a similar "java.lang.NoSuchFieldError:
> alwaysUseFieldBuilders" error any time I do anything memcache related.
>
> HTTP ERROR 500
>
> Problem accessing /stats. Reason:
>
>    alwaysUseFieldBuilders
> Caused by:
>
> java.lang.NoSuchFieldError: alwaysUseFieldBuilders
>        at 
> com.google.appengine.tools.appstats.StatsProtos$RequestStatProto.access$5600(StatsProtos.java:3026)
>        at 
> com.google.appengine.tools.appstats.StatsProtos$RequestStatProto$Builder.maybeForceBuilderInitialization(StatsProtos.java:3590)
>        at 
> com.google.appengine.tools.appstats.StatsProtos$RequestStatProto$Builder.(StatsProtos.java:3582)
>        at 
> com.google.appengine.tools.appstats.StatsProtos$RequestStatProto$Builder.create(StatsProtos.java:3597)
>        at 
> com.google.appengine.tools.appstats.StatsProtos$RequestStatProto$Builder.access$5400(StatsProtos.java:3567)
>        at 
> com.google.appengine.tools.appstats.StatsProtos$RequestStatProto.newBuilder(StatsProtos.java:3554)
>        at 
> com.google.appengine.tools.appstats.MemcacheWriter.begin(MemcacheWriter.java:94)
>        at 
> com.google.appengine.tools.appstats.AppstatsFilter.doFilter(AppstatsFilter.java:117)
>        at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
>        at 
> com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java:58)
>        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:122)
>        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.apphosting.utils.jetty.DevAppEngineWebAppContext.handle(DevAppEngineWebAppContext.java:70)
>        at 
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
>        at 
> com.google.appengine.tools.development.JettyContainerService$ApiProxyHandler.handle(JettyContainerService.java:349)
>        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 org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
>        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
>        at 
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
>        at 
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
>
> cheers
>
> James
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Upcoming changes to Task Queues

[devon.cri...@yahoo.com]

i have bought an app from you (onslaught arena) and it shows up with this 
error what does it mean!??!Error: Server ErrorThe server encountered an 
error and could not complete your request.

If the problem persists, please 
report your 
problem and mention this error message and the query that caused it. 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Using the Channel API with a desktop app: possible?

[Peter Petrov]

This has the drawback that the user must have a Google Account in order to
connect to GTalk. Unfortunately GTalk does not support e.g. SASL ANONYMOUS
logins.

It would be perfect if the Channel API exposed directly its lower-level XMPP
layer. Something like allowing the user to connect via XMPP as
channel_id@app_id.appspotchannel.com using the channel_token as password.

On Sun, Feb 13, 2011 at 11:26 PM, Michael Davidson wrote:

> Another option would be to make an XMPP connection to Google Talk from
> your app (there are XMPP libraries available for many languages), and
> use the XMPP API to send messages to the client.
>
> Michael
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: datastore

[Clinteney]

 basically i am trying to use db.model to store the users information, i am 
just a beginner and dont know if that answers you question. 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: datastore

[yuvi]

Hi,

What authentication method you are planing to use/build ?

On Feb 13, 10:21 pm, Clinteney  wrote:
> Hey, I am trying to create a datastore that stores the users information
> like after he logs in, there is a page that shows his name. So i need the
> datastore for that, right?  but how can I add the new user to the datastore
> after he logs in? thank you

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Using the Channel API with a desktop app: possible?

[Michael Davidson]

Another option would be to make an XMPP connection to Google Talk from
your app (there are XMPP libraries available for many languages), and
use the XMPP API to send messages to the client.

Michael

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: LIFO key name strategy?

[Joseph Letness]

Hi Calvin and Robert, thanks for your replies.  I should have been
more clear about what I am doing, here is some more info:

Calvin, thanks for the link to Ikai's blog post, I haven't seen that
one and it was very interesting.

Robert, here are specific answers to your questions:

>>Why do you say: " I can't use a composite index since it would explode with 
>>my use case"?

I'm using Brett Slatkin's "Relation Index" method of building and
querying set memberships (Google I/O 2009 - Building Scalable, Complex
Apps on App Engine).  According to Brett, using a composite index on
this kind would cause explosion, so any ordering of results will need
to be done in-memory during the request. If the sort order is
immutable, sorted key names can be used to order results based on the
their lexicographical position.

Since a creation timestamp is "immutable" data, I figured that using
lexicographic key names would be the way to go.

>>What would be fine if you could handle your entire result set in one request?

Ordering the result set in-memory.

>>What are you trying to do?

The app is a digital-asset manager.  Users need to be able to query a
set (using the relation index method) and have the results return the
most recent additions first.  The result set could easily be a few
thousand, so I want to use cursor-pagination to display the results
which would preclude any in-memory ordering.

(I'm actually refactoring my existing app that I use to manage/deliver
graphic assets to my clients so that they can add their own data.)

>>Is there a single global LIFO stack, or are there multiple stacks?

The entities are all of the same kind, however, LIFO behavior is
localized to individual user groups.

>>How are new items added to the stack(s)?,  What is the addition rate?

Just one item per user request.  User groups would be just a few
individual users probably less than twenty. The rate per group would
be so low that chances of contention on any sort of accumulator would
be almost nonexistent.

>>Is there a requirement that the items are precisely ordered or are some (or 
>>small) mis-orderings acceptable?

Precision is NOT critical.  Close approximation of chronology is just
fine.


--The auto-generated ids are not strictly increasing

I did not know that.  Thanks!

--Using the current time may also be problematic since the machines
will have slight variations, and in some cases significant variations.

I was aware of that, but since absolute precision is not necessary I
could still use the timestamp as an accumulator if there is some thing
as an "inverse-timestamp algorithm"!?!?

So...

After spending some more time thinking about this, here is what I plan
to do:

Create a counter model kind that is created with an IntegerProperty
starting value of ten billion (I'd like to see somebody reach the
bottom of that!). Give each user group it's own counter and de-count
the values in a transaction (or not, it might be simpler to dismiss
contention and write a handler that ensures uniqueness of the key name
but maintains approximate lexicographic position).  When the counter
value is read, convert the value to a padded string and concatenate it
with the user group name and a leading lowercase letter (k999836/
usergroupname) and use that as the key name for the new asset.

Furthermore, it occurred to me that as a result set is reduced to a
manageable in-memory size, I could test for the length of results and
offer the user the ability to custom order their results (asset name
alphanumeric or asset kind, for example).  Just a thought.

Thanks again for the replies, If anyone thinks there is a better
approach please let me know, I kind of make this stuff up as I go
along..

--Joe


On Feb 12, 10:52 pm, Robert Kluin  wrote:
> Hi Joe,
>   What are you actually trying to do?  Is there a single global LIFO
> stack, or are there multiple stacks?  How are new items added to the
> stack(s)?  In batches to one stack at a time, batches across stacks?
> What is the addition rate?  How are items removed / processed from the
> stack(s)?  Is there a requirement that the items are precisely ordered
> or are some (or small) mis-orderings acceptable?
>
>   Why do you say: " I can't use a composite index since it would
> explode with my use case"?
>
>   The auto-generated ids are not strictly increasing.  What would be
> fine if you could handle your entire result set in one request?
>
>   Using the current time may also be problematic since the machines
> will have slight variations, and in some cases significant variations.
>
> Robert
>
>
>
> On Sat, Feb 12, 2011 at 14:38, Joseph Letness  wrote:
> > Hi everybody, I was wondering if anybody has any good ideas for
> > generating LIFO (Last In FIrst Out) key names.  I can't use a
> > composite index since it would explode with my use case.
>
> > Currently, I can think of two methods:
>
> > Use the auto generated id (which, I believe is accumulative), query
> > for keys only and reverse the

[google-appengine] datastore

[Clinteney]

Hey, I am trying to create a datastore that stores the users information 
like after he logs in, there is a page that shows his name. So i need the 
datastore for that, right?  but how can I add the new user to the datastore 
after he logs in? thank you

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] What happened to appgallery.appspot.com?

[Barry Hunter]

It was removed some time ago.

Partly because it was becoming overrun with spam, there was outdated
information there, but also it was suffering scalablity issues (ie
couldnt cope with the growing number of entries)

... ie Google didnt have the resources for day to day maintaince and
development.


On 13 February 2011 19:17, Ricardo1980  wrote:
> Hi mates!
>
> What happened to appgallery.appspot.com? It is no longer available!
>
> Thanks.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/google-appengine?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] What happened to appgallery.appspot.com?

[Ricardo1980]

Hi mates!

What happened to appgallery.appspot.com? It is no longer available!

Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Blobstore file upload with other form values

[Robert Kluin]

Hi,
  You're getting the IndexError because get_uploads is returning an
empty list, which means there are no blob-info records for the 'file'
field.

  Your other error is because BlobstoreUploadHandler only allows
redirects.  Like Doug suggests, you'll need to redirect to another
page to output something.



Robert





On Sun, Feb 13, 2011 at 02:51, theone  wrote:
> I don't need to return the values. My problem is that while I am able
> to send file with a few form fields, It gives an error using many
> fields:
> w=upload_files[0]
> IndexError: list index out of range
> INFO     2011-02-13 07:43:10,884 dev_appserver_blobstore.py:328]
> Upload handler returned 500
> ERROR    2011-02-13 07:43:10,884 dev_appserver_blobstore.py:341]
> Invalid upload handler response. Only 301, 302 and 303 statuses are
> permitted and it may not have a content body.
> INFO     2011-02-13 07:43:10,910 dev_appserver.py:3317] "POST /_ah/
> upload/agZlcGN2ZGJyHAsSFV9fQmxvYlVwbG9hZFNlc3Npb25fXxjFAgw HTTP/1.1"
> 500 -
>
> In both cases I use the same definitions:
> upload_files = self.get_uploads('file')
> w=upload_files[0]
>
>
>
> On Feb 13, 9:35 am, Doug Anderson  wrote:
>> I have to retract my previous post... this does appear to be working
>> for me.  I can use "self.request.get('description')" to retrieve the
>> text description form field.  My previous problem was that
>> name='descripton' was spelled wrong in my html form (missing the last
>> 'i')... doh!
>>
>> I think your issue is that you lose your "self.response.out.write(N)"
>> content when you redirect via "return self.redirect('/')"... that
>> response body content won't survive the redirect (the redirect will
>> provide its own content).  If you need to return the submitted N and S
>> content then perhaps you could redirect to a URL that takes the 'a'
>> object key as a parameter "self.redirect('/' +
>> urllib.quote(a.key()))".  Of course you'd have to setup your handler
>> to accept the parameter... but then you could re-retrieve 'a' object
>> in the handler via a datastore get such as "a = db.get(a_key)"...
>> assuming 'a_key' is the name of the parameter.
>>
>> On Feb 13, 1:54 am, theone  wrote:
>>
>>
>>
>>
>>
>>
>>
>> > I think you are right about BlobstoreUploadHandler limitations. When I
>> > tried something like:
>> > class X(db.Model):
>> >     N = db.StringProperty()
>> >     S = db.StringProperty()
>> >     F = blobstore.BlobReferenceProperty()
>>
>> > class Upload(blobstore_handlers.BlobstoreUploadHandler):
>> >     def post(self):
>> >         upload_files = self.get_uploads('file')
>> >         a=upload_files[0]
>> >         N = self.request.get('name')
>> >         S = self.request.get('sname')
>> >         if S:
>> >             m=N + S
>> >         else:
>> >             m=S + N
>> >         self.response.out.write(N)
>> >         self.response.out.write(S)
>> >         a=X(N=m, S=S, F=a)
>> >         a.put()
>> >         return self.redirect('/')
>>
>> > It worked partly. I mean I put my model to datastore and file to
>> > blobstore. However, it does not writes the thing like:
>> > self.response.out.write(N). What I understand here we cannot use
>> > everything in BlobstoreUploadHandler.
>>
>> > Also if you request the form fields, it does not work.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/google-appengine?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: AddAppVersion failed: DEADLINE_EXCEEDED

[satish]

I just checked again today and the problem is gone. May be, appengine was 
having some problems yesterday

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Is it impossible to guarantee a put()

[stevep]

Hi Robert,

Thanks for your input.

Here's a summary, and wrap-up for me as I've decided on this path for
now.

First, I'll note that all the data coming in is compressed. No
opportunity there to squeeze below the current TQ limit.

My current strategy for architecture design should hopefully minimize
put() failures in the on-line handler, and provide good, solid, backup
(solid with respect to business not just technical risks).

1) Use a high replication handler.
2) Strip all but the most essential indexes from the main record which
will be put() in the on-line handler. Handle indexes in a separate,
related db class via the task queue.
3) Maintain an Amazon Web Server for handling put() failures at GAE.

Hopefully Google's SLA-like inferences about high replication bear
fruit. Perhaps at some point we'll get past the beta label and get
something from them more specific. For now I'll trust the "Do no evil"
slogan, and will also trust what appears to be a well-grounded and
talented group of engineers (based solely on my readings of their
forum posts and seeing GAE develop).

My conclusion about custom indexes is based on latencies for some
early development work that had some activity as a master/slave app.
Clearly (and this has been alluded by in these forums by Googlers)
custom indexes need careful consideration because of the put()
overhead. Fortunately for what we are doing we can separate the index
from the main file using the allocated-id to link back. Pushing the
indexed update into the task queue is probably the most important
change as we provide a good number of user slice/dice filters to
access the site content. If Google could do one case study, I'd vote
for this area so that we could have a better understanding of how
custom indexes affect put() performance.

Of all your work-arounds, my belief is that running an AWS server for
saving failed writes is going to be the best. There are important
business-risk considerations at play here not just technical. I wont
go into these in detail, but suffice it to say that I'll be happier
when Google removes the beta label – and I say this not just out of
selfish interests, but because I believe that GAE is really
disruptive, leverages a very key Google core company competency, and
deserves to gain strategic commitment from Larry (or whomever) as a
full enterprise-class product. Think shareholders and developers, and
the GAE team all deserve this.

Summary: Overall I am not unhappy having to rework how my put()s are
done. I think the new approach will be much better suited to an app
that is optimized not just for lower failure rates, but for optimized
operation within the GAE infrastructure (but I'm clearly guessing
about the latter point).

Having said that, I am still hopeful that Google's talented GAE group
will consider providing a task queue that can accept that same data
payload as the on-line handler. It's obvious why they will not do this
for a TQ that can accept large numbers of tasks. Likely it would be
simple for them to provide a limit on this queue related to the number
of available tasks so that the memory/storage requirements for this TQ
are not abused by us developers who are always looking for that easy
workaround. TQ's are great IMHO, and I'd like to utilize them as much
as possible.

We’re going live soon, so I think this will be my last long
architecture thread. Thanks for all who have helped, most notably
Robert whose great inputs for nearly every forum thread (not just
mine) have been tremendously helpful. (Note to Google: if you’re
helping Robert financially, you’re getting a great return. If not, do
so.)

cheers,
stevep
(who had a good night's sleep, hence the verbosity of this reply)

On Feb 12, 9:11 pm, Robert Kluin  wrote:
> Hey Steve,
>   First, "[t]hink of your client's put() as your customer's head, and
> the 503 as the brick wall" is great, it is humorous and accurate
> analogy.  I can relate.  And, I also deal with low-write-rate but
> extremely high-value writes in some apps.  It is tricky and makes
> small failures / blips a much more significant issue.
>
>   In any client-server app, there will occasionally be communication /
> server-side issues.  Have you thought about storing data locally on
> submit (or only if there is a server-side error) then implementing
> some type of start-up recovery logic that will retry the save?  Could
> be particularly helpful if you have some way of making the write
> idempotent (ie using a key_name). I know it is not perfect but it
> could help out a bit.  There are some little tools that might help
> with this, like lawnchair (http://westcoastlogic.com/lawnchair/).  If
> you couple that with saving via an AJAX call, even in an error
> situation the user experience would be at least a little better.
>
>   Another question, how far over the 10K limit are you?  Have you
> tried using bzip to compress your data?  Perhaps if you compress the
> payload it would be possible to enqueue it in a t

Re: [google-appengine] App Engine SDK 1.4.2 is out!

[Geoffrey Spear]

Are you using appstats or some other middlewear that might be using 
webapp.template?  You need to call use_library() before any code tries to 
use django; app_config.py is probably a good place to put the call.

On Sunday, February 13, 2011 10:44:38 AM UTC-5, $ÂÑЀ€P wrote:
>
> Hi,
>
> tried to use use_library('django','1.2')
>
> This is giving this kind of error..., can any one help how to sort 
> this...
>
> E2011-02-13 07:08:52.561 
>
> : django 1.2 
> was requested, but 0.96.4.None is already in use
> Traceback (most recent call last):
>   File 
> "/base/data/home/apps/littleparadischool/1-2-36.348324395325175647/cricket/disxml.py",
>  line 7, in 
> use_library('django', '1.2')
>   File 
> "/base/python_runtime/python_lib/versions/1/google/appengine/dist/_library.py",
>  line 291, in use_library
> InstallLibrary(name, version, explicit=True)
>   File 
> "/base/python_runtime/python_lib/versions/1/google/appengine/dist/_library.py",
>  line 250, in InstallLibrary
> CheckInstalledVersion(name, version, explicit=True)
>   File 
> "/base/python_runtime/python_lib/versions/1/google/appengine/dist/_library.py",
>  line 194, in CheckInstalledVersion
> (name, desired_version, installed_version))
>
>
> On Sun, Feb 13, 2011 at 6:01 AM, David Mora  wrote:
>
>> There seems to be a problem (in python) when using the bulk loader:
>>
>> UnacceptableVersionError: django 1.1 was requested, but 1.2.3.final.0
>> is already in use
>> [INFO] An error occurred. Shutting down...
>>
>> We load django 1.1 directly in app_config.py so it is used across all
>> mapreduces/pipelines
>>
>> Would not say it is a issue yet since i have not properly debug it
>> (hell, is weekend :) ) - if i found more info ill fill up a bug
>> properly, thought i should share this, tho
>>
>> On 12 February 2011 14:30, Sandeep Koduri  wrote:
>> > Thanks for the update, we were eager about this.
>> > Thinking why the version release updates of python went after java ones,
>> > different from regular process.
>> > This version helps us lot
>> >
>> > On Sat, Feb 12, 2011 at 1:50 AM, Ikai Lan (Google)
>> >  wrote:
>> >>
>> >> Hey everyone,
>> >> The moment you've been waiting for is here. Drum roll please ... *drum
>> >> roll* SDK 1.4.2 is out! I know you've all been anxious to get your 
>> hands on
>> >> this release (many of you jumping the gun and download the SDK before 
>> the
>> >> previous announcement). You won't be disappointed. Here's the official 
>> blog
>> >> post:
>> >>
>> >> 
>> http://googleappengine.blogspot.com/2011/02/app-engine-142-sdk-api-updates-and.html
>> >> One thing you'll notice is that Prospective Search (Matcher API) isn't 
>> in
>> >> this release even though it was in the prerelease SDK. We're going to 
>> try to
>> >> get it out for one of the upcoming releases. Apologies for those of you
>> >> wanted to use it - it's coming soon, I promise!
>> >> Release notes for 1.4.2 are below. As usual, you can update the SDK
>> >> through all the standard means or via the downloads
>> >> page: http://code.google.com/appengine/downloads.html
>> >> Note: Some of you who downloaded the Java SDK prior to this 
>> announcement
>> >> actually got a version that was missing the unit testing jars. If you
>> >> downloaded the Java SDK over ~30 minutes ago and are wondering where 
>> all the
>> >> testing jars went, please go ahead and download it again (if you didn't
>> >> notice that the testing jars were missing ... well, shame on you, you 
>> should
>> >> be writing unit tests).
>> >> Java Version 1.4.2
>> >> =
>> >> - You can now vacuum datastore indexes with the Java SDK.
>> >> - The XMPP API was updated to include presence and allow subscriptions.
>> >> - The Task Queue now supports programmatic deleting of tasks.
>> >> http://code.google.com/p/googleappengine/issues/detail?id=2588
>> >> - The maximum rate per queue at which tasks are processed has been
>> >> increased to
>> >>   100 task per second.
>> >> - The maximum number of concurrent requests for a single queue can be
>> >> specified
>> >>   in the application's queue.xml. This provides an additional 
>> easy-to-use
>> >> form
>> >>   of rate limiting. The current number of running tasks is also 
>> displayed
>> >> in
>> >>   the Admin Console.
>> >> - Metadata queries in the Datastore now support cursors.
>> >> - Admin Console logs viewer now displays time as -MM-DD 
>> HH:MM:SS.mmm.
>> >> - Added a warning when an admin tries to upload a queue.yaml where the
>> >> number
>> >>   of new queues and the number of disabled queues exceeds 100.
>> >> - Added a putIfUntouched() method to the Memcache API.
>> >> http://code.google.com/p/googleappengine/issues/detail?id=2139
>> >> - Added JAX-WS support for writing SOAP clients and SAAJ support for
>> >> writing
>> >>   SOAP servers. JAX-WS for SOAP servers is not yet supported.
>> >> - The Mail API added KML and KMZ files as allowed attachments.
>> >> - Fixed an issue where mail from @

[google-appengine] Query __BlobInfo__ and WHERE BlobKey is in BlobInfo

[branflake2267]

I was having a hard time figuring out the query possibilities for 
__BlobInfo__ WHERE BlobKey='[blobkey_str]'.

Here is my list of query possibilities to get the blob:
http://code.google.com/p/gwt-examples/wiki/DemoGAEMultiFileBlobUpload?ts=1297612267#Querying

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] App Engine SDK 1.4.2 is out!

[Sandeep Koduri]

Hi,

tried to use use_library('django','1.2')

This is giving this kind of error..., can any one help how to sort
this...

E2011-02-13 07:08:52.561

:
django 1.2 was requested, but 0.96.4.None is already in use
Traceback (most recent call last):
  File 
"/base/data/home/apps/littleparadischool/1-2-36.348324395325175647/cricket/disxml.py",
line 7, in 
use_library('django', '1.2')
  File 
"/base/python_runtime/python_lib/versions/1/google/appengine/dist/_library.py",
line 291, in use_library
InstallLibrary(name, version, explicit=True)
  File 
"/base/python_runtime/python_lib/versions/1/google/appengine/dist/_library.py",
line 250, in InstallLibrary
CheckInstalledVersion(name, version, explicit=True)
  File 
"/base/python_runtime/python_lib/versions/1/google/appengine/dist/_library.py",
line 194, in CheckInstalledVersion
(name, desired_version, installed_version))


On Sun, Feb 13, 2011 at 6:01 AM, David Mora  wrote:

> There seems to be a problem (in python) when using the bulk loader:
>
> UnacceptableVersionError: django 1.1 was requested, but 1.2.3.final.0
> is already in use
> [INFO] An error occurred. Shutting down...
>
> We load django 1.1 directly in app_config.py so it is used across all
> mapreduces/pipelines
>
> Would not say it is a issue yet since i have not properly debug it
> (hell, is weekend :) ) - if i found more info ill fill up a bug
> properly, thought i should share this, tho
>
> On 12 February 2011 14:30, Sandeep Koduri 
> wrote:
> > Thanks for the update, we were eager about this.
> > Thinking why the version release updates of python went after java ones,
> > different from regular process.
> > This version helps us lot
> >
> > On Sat, Feb 12, 2011 at 1:50 AM, Ikai Lan (Google)
> >  wrote:
> >>
> >> Hey everyone,
> >> The moment you've been waiting for is here. Drum roll please ... *drum
> >> roll* SDK 1.4.2 is out! I know you've all been anxious to get your hands
> on
> >> this release (many of you jumping the gun and download the SDK before
> the
> >> previous announcement). You won't be disappointed. Here's the official
> blog
> >> post:
> >>
> >>
> http://googleappengine.blogspot.com/2011/02/app-engine-142-sdk-api-updates-and.html
> >> One thing you'll notice is that Prospective Search (Matcher API) isn't
> in
> >> this release even though it was in the prerelease SDK. We're going to
> try to
> >> get it out for one of the upcoming releases. Apologies for those of you
> >> wanted to use it - it's coming soon, I promise!
> >> Release notes for 1.4.2 are below. As usual, you can update the SDK
> >> through all the standard means or via the downloads
> >> page: http://code.google.com/appengine/downloads.html
> >> Note: Some of you who downloaded the Java SDK prior to this announcement
> >> actually got a version that was missing the unit testing jars. If you
> >> downloaded the Java SDK over ~30 minutes ago and are wondering where all
> the
> >> testing jars went, please go ahead and download it again (if you didn't
> >> notice that the testing jars were missing ... well, shame on you, you
> should
> >> be writing unit tests).
> >> Java Version 1.4.2
> >> =
> >> - You can now vacuum datastore indexes with the Java SDK.
> >> - The XMPP API was updated to include presence and allow subscriptions.
> >> - The Task Queue now supports programmatic deleting of tasks.
> >> http://code.google.com/p/googleappengine/issues/detail?id=2588
> >> - The maximum rate per queue at which tasks are processed has been
> >> increased to
> >>   100 task per second.
> >> - The maximum number of concurrent requests for a single queue can be
> >> specified
> >>   in the application's queue.xml. This provides an additional
> easy-to-use
> >> form
> >>   of rate limiting. The current number of running tasks is also
> displayed
> >> in
> >>   the Admin Console.
> >> - Metadata queries in the Datastore now support cursors.
> >> - Admin Console logs viewer now displays time as -MM-DD
> HH:MM:SS.mmm.
> >> - Added a warning when an admin tries to upload a queue.yaml where the
> >> number
> >>   of new queues and the number of disabled queues exceeds 100.
> >> - Added a putIfUntouched() method to the Memcache API.
> >> http://code.google.com/p/googleappengine/issues/detail?id=2139
> >> - Added JAX-WS support for writing SOAP clients and SAAJ support for
> >> writing
> >>   SOAP servers. JAX-WS for SOAP servers is not yet supported.
> >> - The Mail API added KML and KMZ files as allowed attachments.
> >> - Fixed an issue where mail from @appid.appspotmail.com did not work
> when
> >>   sending mail to app admins.
> >> - Fixed an issue where the SDK did not enforce the 100 task limit for
> the
> >> Task
> >>   Queue.
> >> http://code.google.com/p/googleappengine/issues/detail?id=3296
> >> - Fixed an issue where the Java SDK URLFetch did not support 32MB
> response
> >>   sizes.
> >> http://code.google.com/p/googleappengine/issues/detail?id=4215
> >> - Fixed an

[google-appengine] Re: AddAppVersion failed: DEADLINE_EXCEEDED

[Jason]

I was not able to find the cause.  It just stopped happening after a
couple hours.

On Feb 12, 10:54 pm, satish  wrote:
> Jason, Were able to find out the cause of this error? I am seeing the same
> issue.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Channel API client 'open' command fails silently

[Parham]

Hi,

1. We are using Channel API on our website and it works very well on desktop 
and mobile site (iPhone/Android). But the same code fails silently on 'open' 
command in our mobile app (built with Appcelerator 
Titanium/jQTouch/WebView). Unfortunately it's not possible to debug 
JavaScript in Titanium/WebViews. What are the possible causes of this? 

2. What are the compatibility requirements for the JavaScript Client? In our 
test it didn't work on S60V5 browsers (Nokia N97/5800).

3. There was a bug with 'close' command which required to manually remove 
the iframe, is it fixed in latest release (1.4.2)?

Thanks,
Parham.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.