Re: [google-appengine] Prerelease SDK 1.3.5 is out!

[Bart Thate]

On Wed, Jun 16, 2010 at 8:11 PM, Ikai L (Google)  wrote:
> Hey developers!

Hoi Ikai !

> We've release the prerelease SDK for 1.3.5. Get it here:
> http://code.google.com/p/googleappengine/downloads/list
> If you want to try out new features locally before they go live, here's your
> chance. We welcome any feedback you have.

I get the following when uploading my bot to GAE ..

Closing update: new version is ready to start serving.
Uploading index definitions.
Uploading cron entries.
Error 404: --- begin server output ---



404 Not Found


Error: Not Found
The requested URL
/api/cron/update?version=1&app_id=jsoncloud was not
found on this server.


--- end server output ---

Must say i have no clue as what this is ;]

Bart

-- 
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-appeng...@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: RSS Feed Aggregator

[Bart Thate]

Hoi !

On 25 aug, 20:36, nevets1219  wrote:
> I would like to create an aggregator that would retrieve on a set
> interval RSS feeds from a list of feeds and optionally filter/alter/
> categorize/etc the feeds retrieved, let's call this the "big list".
> Then I would like to retrieve the "big list" to read in Thunderbird
> (or some other application of choice).
>
> I want to do it this way since Thunderbird may not always be on (my
> computer will not always be on) and I think RSS retrieves latest
> entries which may exclude older entries that you haven't seen.
>
> I believe an aggregator is quite doable with Google AppEngine, please
> correct me if I'm wrong. However, I'm not quite sure how to approach
> the problem of defining what's new. I'm guessing the client retrieves
> and based on what it already has marks entries as new but how would I
> know in my aggregator what has been retrieved and what hasn't (without
> a manual process)?

I made a bot that does feed fetching and forwards new entries to
xmpp,web and wave based on the "updated" field of the feed. This way
you only need to maintain a timestamp of the last viewed entry of the
feed so that anything newer gets forwarded, anything older gets
dropped.

See http://jsonbot.appspot.com for a running instance of the bot, it's
this in alpha though so i'm sure things ain't working yet as they
should ;]

Grtx,

Bart

-- 
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-appeng...@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] JSONBOT 0.3 RELEASE

[Bart Thate]

Hello world !

I just released version 0.3 of JSONBOT. JSONBOT is a remote event
driven framework for building bots that talk JSON to each other over
XMPP.

This distribution provides bots built on this framework for console,
IRC, XMPP for the shell and WWW and XMPP for the Google Application
engine.

JSONBOT 0.3 provides the following programs:

jsb - console version of jsonbot
jsb-import - import data from another bot
jsb-installplug - install remote plugins
jsb-irc - IRC version of jsonbot (socket)
jsb-xmpp - XMPP version of jsonbot (socket)
jsb-fleet - mix IRC and XMPP bots
jsb-release - create a new release directory
jsb-rollback - rollback a release
jsb-run - run a release in the GAE dev_appserver
jsb-stop - stop a running bot
jsb-upload - upload a release to the GAE

A plugin infrastructure is in place to program the functionality that
is needed.

JSONBOT 0.3 plugins:

8b - eight ball
admin - administator related commands
alias - keep aliases (per user)
ask - plugin for asking "experts" a question
choice - choice out of a list .. used in pipelines
controlchar - set the control character of a channel
forward - forward events of a channel to another bot
clone - clone waves into new ones
core - core bot commands
count - count the numbers in a result .. used in pipelines
data - provide data dumps of channels, bots, events
fleet - support multiple bots in a running instance (list of bots)
gae - provide GAE commands like flush cache or cache stats
gadget - wave gadget support
gcalc - use google to calculate
grep - grep the result .. used in pipelines
hubbub - pubsubhubbub plugin providing subscribe functionality
ipcalc - ipcalculator
irc - IRC related commands
jsondata - enable/disable sharing of files through the jsonserver (not
enabled right now)
kickban - channel control commands for IRC
misc - other commands
more - do a more on buffered output
nickcapture - retake nick (IRC)
nickserv - nickserver support (IRC)
not - negated grep .. used in pipelines
outputcache - show outputcache data
rss - provide RSS and Atom pollers
relay - relay to other waves/xmpp
restserver - provide REST functionality to the bot
reload - reloading of plugins
reverse - rever see the result .. also used in pipelines
seen - keep track of users
shop - keep shopping lists
sort - sort the result .. used in pipelines
tail - tail the result .. used in pipelines
test - test commands
tinyurl - get a tinyurl
todo - keep a todo list
underauth - undernet auth support (IRC)
uniq - make the result unique .. used in pipelines
user - user management
userstate - userstate management
watcher - watch channels that get forwarded to the bot.
wave - wave related commands
weather - show weather in a city
welcome - welcome messages shown in the gadget
wikipedia - query wikipedia
xmpp - xmpp related functions account

Project home is at http://jsonbot.googlecode.com

Have fun with 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-appeng...@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] server irc

[Bart Thate]

Hello all ;]


On Thu, Sep 16, 2010 at 1:04 AM, Robert Kluin wrote:

> Not to mention that AppEngine only speaks HTTP.
>
>
>
AppEngine can also do xmpp.

You can relay IRC messages to AppEngine. My bot can be used to send events
on an IRC bot over to AppEngine for example. It uses jabber (xmpp) send
these events over.
The other way around, web or xmpp from AppEngine to IRC is also possible.

Take a look at http://jsonbot.googlecode.com if you are interested

Greets,

Bart

>
>
>
> On Wed, Sep 15, 2010 at 16:58, Barry Hunter 
> wrote:
> > I doubt it will as such.
> >
> > AppEngine is designed to respond to requests. The most common being a
> > web-request. So a request comes in, a script runs for a short time and
> > returns the responce.
> > (it also responds to background tasks etc)
> >
> > A IRC server would pretty much need to run continouslly and read and
> > possibly respond to messages.
> >
> > No of course it might be /possible/ with a some crafty hacking, but
> > its not what appengine was designed for, so it wont be an easy fit.
> >
> >
> >
> >
> > On 15 September 2010 15:09, Luis Díaz  wrote:
> >> Greetings!
> >>
> >> anyone knows how to implement an irc server in GAE
> >>
> >> using python.
> >>
> >> I have not much information on irc.
> >> there are free servers .. or nodes
> >>  but I would like to implement your own to manage my taste
> >>
> >> --
> >> Díaz Luis
> >> TSU Analisis de Sistemas
> >> Universidad de Carabobo
> >>
> >> --
> >> 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-appeng...@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-appeng...@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-appeng...@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-appeng...@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] JSONBOT 0.4 RELEASED

[Bart Thate]

Yesterday i pushed version 0.4 of JSONBOT to pypi and googlecode. This
version has a rewritten core that makes it easier to develop bots for
and has lots of bugs fixed. A karma plugin was added as well as a
silent mode that forwards bot responses to /msg.

You can grab a copy on http://jsonbot.googlecode.com or use the
mercurial reposistory:

"hg clone http://jsonbot.googlecode.com/hg jsonbot".

please file any bugs reports at http://code.google.com/p/jsonbot/issues/list

we are at #dunkbots on freenode and IRCnet.

Have fun !

about JSONBOT:
JSONBOT is a remote event-driven framework for building bots that talk
JSON to each other over XMPP. IRC/Console/XMPP (shell) Wave/Web/XMPP
(GAE) implementations provided.

-- 
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-appeng...@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] JSONBOT 0.4 RELEASED

[Bart Thate]

Thanks Ikai, glad you like it ;]

Bart

On Thu, Sep 30, 2010 at 11:57 PM, Ikai Lan (Google) <
ikai.l+gro...@google.com > wrote:

> Awesome! I've added this to the Open Source projects page:
>
>
> http://groups.google.com/group/google-appengine/web/google-app-engine-open-source-projects
>
> --
> Ikai Lan
> Developer Programs Engineer, Google App Engine
> Blogger: http://googleappengine.blogspot.com
> Reddit: http://www.reddit.com/r/appengine
> Twitter: http://twitter.com/app_engine
>
>
>
> On Tue, Sep 28, 2010 at 2:22 PM, Bart Thate  wrote:
>
>> Yesterday i pushed version 0.4 of JSONBOT to pypi and googlecode. This
>> version has a rewritten core that makes it easier to develop bots for
>> and has lots of bugs fixed. A karma plugin was added as well as a
>> silent mode that forwards bot responses to /msg.
>>
>> You can grab a copy on http://jsonbot.googlecode.com or use the
>> mercurial reposistory:
>>
>> "hg clone http://jsonbot.googlecode.com/hg jsonbot".
>>
>> please file any bugs reports at
>> http://code.google.com/p/jsonbot/issues/list
>>
>> we are at #dunkbots on freenode and IRCnet.
>>
>> Have fun !
>>
>> about JSONBOT:
>> JSONBOT is a remote event-driven framework for building bots that talk
>> JSON to each other over XMPP. IRC/Console/XMPP (shell) Wave/Web/XMPP
>> (GAE) implementations provided.
>>
>> --
>> 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-appeng...@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-appeng...@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-appeng...@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] error rate

[Bart Thate]

I also have problems, site takes no traffic at all apart from a rss
fetcher every minute and the occaisional drive by user ;] These logs
are related to the user dispatching code not the rss fetcher (has an
error rate of ~ 10%).

appid: jsonbot

error rate: /dispatch/ 185   41%

log snippet:

10-11 01:19PM 46.659 /dispatch/ 500 42155ms 0cpu_ms 0kb Mozilla/5.0
(X11; U; Linux x86_64; en-
10-11 12:49PM 46.652 /dispatch/ 500 42255ms 8cpu_ms 8api_cpu_ms 0kb
Mozilla/5.0 (X11; U; L
10-11 12:44PM 46.674 /dispatch/ 500 30286ms 200cpu_ms 1kb Mozilla/5.0
(X11; U; Linux x86_64;
10-11 12:24PM 46.668 /dispatch/ 500 43332ms 0cpu_ms 0kb Mozilla/5.0
(X11; U; Linux x86_64;
10-11 11:19AM 46.670 /dispatch/ 500 29312ms 160cpu_ms 0kb Mozilla/5.0
(X11; U; Linux x86_64;
10-11 10:09AM 46.627 /dispatch/ 500 43723ms 0cpu_ms 0kb Mozilla/5.0
(X11; U; Linux x86_64; e
10-11 10:09AM 46.672 /dispatch/ 500 10520ms 0cpu_ms 0kb Mozilla/5.0
(X11; U; Linux x86_64; en-
10-11 10:09AM 46.659 /dispatch/ 500 10532ms 0cpu_ms 0kb Mozilla/5.0
(X11; U; Linux x86_64; en-

>1ms 500:

A serious problem was encountered with the process that handled this
request, causing it to exit. This is likely to cause a new process to
be used for the next request to your application. If you see this
message frequently, you should contact the App Engine team. (Error
code 203)

~1 ms 500:

Request was aborted after waiting too long to attempt to service your
request. This may happen sporadically when the App Engine serving
cluster is under unexpectedly high or uneven load. If you see this
message frequently, please contact the App Engine team.

normal:

10-11 01:49PM 46.707 /dispatch/ 200 100ms 59cpu_ms 0kb Mozilla/5.0
(X11; U; Linux x86_64; en-
10-11 01:49PM 46.681 /dispatch/ 200 82ms 59cpu_ms 0kb Mozilla/5.0
(X11; U; Linux x86_64; en
10-11 01:49PM 46.661 /dispatch/ 200 58ms 60cpu_ms 0kb Mozilla/5.0
(X11; U; Linux x86_64; en-

Hope this helps,

Bart

-- 
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-appeng...@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] ssl and openid

[Bart Thate]

Hoi everybody !

In the prerelease version it is mentioned that SSL with openid would be
fixed, but i seen no mention of it in the official release notes. After
testing this it still doesn't work for me, is this supposed to be fixed or
do we need to wait till the next release ?

Bart

-- 
@jsonbot Heerhugowaard, Netherlands
programming schizofrenic - http://jsonbot.appspot.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-appeng...@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] Valid filename

[Bart Thate]

When i upload my bot to the GAE i get these errors:

2010-10-16 06:46:18,789 ERROR appcfg.py:1506 Invalid character in filename:
gozerdata/channels/~...@127.0.0.1
2010-10-16 06:46:18,789 ERROR appcfg.py:1506 Invalid character in filename:
gozerdata/channels/#dunkbots
2010-10-16 06:46:18,789 ERROR appcfg.py:1506 Invalid character in filename:
gozerdata/channels/d...@9cb22b89-142e-482f-bd8b-046a95c38d7f

How can i normalize my filename so i get a correct filename ?
What characters are allowed and what not?  Is there any function i can call
to strip them ?

Thnx !

Bart
-- 
@jsonbot Heerhugowaard, Netherlands
programming schizofrenic - http://jsonbot.appspot.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-appeng...@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: Weird Upload Errors

[Bart Thate]

Same here, can take ages for an upload to finish. Just loops the 60 second
dance.

On Mon, Oct 18, 2010 at 10:38 PM, dloomer  wrote:

> I should note I'm not getting the 403 or 409 error, just the repeated
> "will check again in 60 seconds" until it gives up with "version not
> ready."
>
> On Oct 18, 3:35 pm, Amir  Michail  wrote:
> > On Oct 18, 4:18 pm, J  wrote:
> >
> > > Hi,
> >
> > > Hopefully someone can shed some light on this: all of a sudden, I
> > > started receiving '409' errors. For example,
> >
> > I can't deploy a new version of an app.  It just keeps saying "Will
> > check again in 60 seconds."
> >
> > I don't see the 409 error.
> >
> > Amir
> >
> >
> >
> >
> >
> > > ...
> > > ...
> > > Will check again in 32 seconds.
> > > Checking if new version is ready to serve.
> > > Will check again in 60 seconds.
> > > Checking if new version is ready to serve.
> > > Will check again in 60 seconds.
> > > Checking if new version is ready to serve.
> > > Will check again in 60 seconds.
> > > Checking if new version is ready to serve.
> > > Will check again in 60 seconds.
> > > Checking if new version is ready to serve.
> > > 2010-10-18 16:14:18,997 INFO appcfg.py:1814 HTTP Error (HTTP Error
> > > 409: Conflict)
> > > Rolling back the update.
> > > Error 409: --- begin server output ---
> > > No transaction is in progress.
> > > --- end server output ---
> >
> > > It has happened a couple of times already.
> >
> > > Thanks in advance.
>
> --
> 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-appeng...@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.
>
>


-- 
@jsonbot Heerhugowaard, Netherlands
programming schizofrenic - http://jsonbot.appspot.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-appeng...@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] too lame for words

[Bart Thate]

So i was programming the whole day and night to give my website a new look,
finally got something working and tweeted the website url -
http://jsonbot.appspot.com. I was so amazed the bot loaded that fast i
though man i must be king of optimisation, seeing my website work as it
should (latency ~ 150msec).

But then after a few visitors, it just went dead throwing 500's all the
time.

*Instances*QPSLatencyMemory0.01732648.0 ms8.2 MBytes0.01732951.0 ms8.0
MBytes0.01732914.0 ms7.9 MBytes0.01733.0 ms10.3 MBytes

ENOCLUE whats going on here, but it sure is disappointing. Seems to me that
coldstart is a problem on GAE right now and scaling doesnt work at all cause
that always needs to cold boot new instances up to be able to scale ?

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.
I hope google can give also us "freerunners" a decent level of service so
that we can grow as well.
The app is still stuck, i wont upload a new one till you have been able to
take a look at it.

appid: jsonbot

Regards,

Bart


-- 
@jsonbot Heerhugowaard, Netherlands
programming schizofrenic - http://jsonbot.appspot.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-appeng...@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: too lame for words

[Bart Thate]

On Sat, Oct 30, 2010 at 1:35 AM, Tim Hoffman  wrote:

> Hi
>
>
Hi Tim,

you are right looking at the logs is the first thing i should do ..


   1. 10-29 04:36PM 12.953

   botbase - on demand reloading of commonplugs.forward

   2. D10-29 04:36PM 12.953

   plugins - trying commonplugs.forward

   3. E10-29 04:36PM 50.560

   :
   Traceback (most recent call last):



Its all deadline errors, notice the time difference between the last debug
line and the exception .. 38 seconds ??

I dont use django but my own framework is getting huge and loading that
might be a problem. Real problem is though that i cant know for sure whether
its my code at fault or its appengine that has troubles. Its getting hard to
develop on a unstable platform ;[



I suggest you do some serious logging in your app so you can see where
> the time is taken up.  If its during initial imports
> then you may be in a pocket of poor performing appengine
> infrastructure at the moment.  (A few people seem to be having
> onoing problems since the 27th)  In addition  it will give you a
> better insight into how you app is behaving during startup.
>
> It's also possible that you got a DeadLineExceeded during startup that
> has left you with a broken instance (this can happen if you using
> things
> like django).
>
> Have a look at the system log and see if all the 500's are due to
> DeadLineExceeded or just the first one followed by
> ImportError's or even AttributeError  in seemingly odd places.
>
>
its all DeadLineExceeded errors.



> Mind you all of this only applies if your using python.  (I have no
> idea haw the java platforms behave)
>
>
I'm on python. If you're curious about the code its on
http://jsonbot.googlecode.com


> Rgds
>
> Tim


Thanks for the help Tim !

Bart




> On Oct 30, 7:28 am, Bart Thate  wrote:
> > So i was programming the whole day and night to give my website a new
> look,
> > finally got something working and tweeted the website url -
> http://jsonbot.appspot.com. I was so amazed the bot loaded that fast i
> > though man i must be king of optimisation, seeing my website work as it
> > should (latency ~ 150msec).
> >
> > But then after a few visitors, it just went dead throwing 500's all the
> > time.
> >
> > *Instances*QPSLatencyMemory0.01732648.0 ms8.2 MBytes0.01732951.0 ms8.0
> > MBytes0.01732914.0 ms7.9 MBytes0.01733.0 ms10.3 MBytes
> >
> > ENOCLUE whats going on here, but it sure is disappointing. Seems to me
> that
> > coldstart is a problem on GAE right now and scaling doesnt work at all
> cause
> > that always needs to cold boot new instances up to be able to scale ?
> >
> > Error: Server ErrorThe server encountered an error and could not complete
> > your request.
> >
> > If the problem persists, please
> > report<http://code.google.com/appengine/community.html> your
> > problem and mention this error message and the query that caused it.
> > I hope google can give also us "freerunners" a decent level of service so
> > that we can grow as well.
> > The app is still stuck, i wont upload a new one till you have been able
> to
> > take a look at it.
> >
> > appid: jsonbot
> >
> > Regards,
> >
> > Bart
> >
> > --
> > @jsonbot Heerhugowaard, Netherlands
> > programming schizofrenic -http://jsonbot.appspot.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-appeng...@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.
>
>


-- 
@jsonbot Heerhugowaard, Netherlands
programming schizofrenic - http://jsonbot.appspot.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-appeng...@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: too lame for words

[Bart Thate]

I uploaded my bot to one of my other projects ...
http://jsonspot.appspot.com, seems to run fine there (dont know if it would
scale and then give problems).

Bart

-- 
@jsonbot Heerhugowaard, Netherlands
programming schizofrenic - http://jsonbot.appspot.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-appeng...@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: too lame for words

[Bart Thate]

On Sat, Oct 30, 2010 at 2:35 AM, Tim Hoffman  wrote:

> Hi Bart
>
>
Re Tim ;]


> When you have successful startup what sort of average startup time are
> you seeing.  (I would accumulate a fair number of stats on this
> so you can see what a successful varience is.)  My startup time for (a
> non django) but large stack is typically under 6 secs on a good day
> 8-12 secs when things are a bit slow and DEE when it's bad ;-)  In the
> last few days I am seeing a DEE about 5 times a day on a startup
> from a very quiet site (its a actually a test site so no one is using
> it).
>
>
At http://jsonspot.appspot.com (running fine it seems) the startup time of a
cold boot is:

10-29 05:39PM 02.915 /dispatch/ 200 2387ms 958cpu_ms 25api_cpu_ms

 rest of the dispatches are at 100-150 msec.

I would also have a closer look and see if a request just after a DEE
> is also failing but with shorter time.  Big frameworks can have
> problems
> if they don't start up cleanly.
>
>
I think the cluster on which jsonbot runs is bork or something as jsonspot
seems to do fine.



> Ultimately appengine will fail at some point (and come back). Like the
> datastore - you will get a timeout at some point, memcache - stuff
> will be
> purged)  it means you do have to code for or allow for the fact that
> things may go wrong for a period.  Hopefully not often.  The big
> upside though
> is if you take into account these sorts of things your app will be
> more robust. It still beats managing hardware ;-)
>
>
I wonder how much requests i could run on 1 hosted box. Way easier to
program thats for sure. The more i get into the appengine programming (guess
about a year now or so) the more i wonder if the limitations of appengine
are worth the problems.

Actually i'm not into running 1 big instance of my program for millions of
users, my plan is to let every user run his/hers own bot. One of the
advantadges of open sourcing your code ;]



> Profiling your startup will also help you shrink startup time.  Maybe
> there are things you can defer till you need them.  This won't help
> if google is having a really bad day. But it will overall improve your
> responsiveness when you do have to start new instances.
>
>
I started porting my then console gozerbot to the GAE and had to
drastiscally change away from the monolitic load every thing at once, to
seperate handlers and on demand loading of my plugins etc etc. I have
appstat running so i'll certainly will take a look into profiling startup.

One note to make though is that i'm trying not to be a whiner, i love
appengine and have learned a lot on this platform the last year. I'm
gratefull to google to giving me this opportunity but i must say that i have
serious doubts if the CGI method of execution isn't too much of a strain on
the programming side compared to the gains i would get from hosting my site
with google. I really hate this 30 sec boundary ;[


> Rgds
>
> Tim
>
>
Thnx for giving your energy and advise Tim, it's much appreciated ;]

Bart



> On Oct 30, 7:50 am, Bart Thate  wrote:
> > On Sat, Oct 30, 2010 at 1:35 AM, Tim Hoffman  wrote:
> > > Hi
> >
> > Hi Tim,
> >
> > you are right looking at the logs is the first thing i should do ..
> >
> >1. 10-29 04:36PM 12.953
> >
> >botbase - on demand reloading of commonplugs.forward
> >
> >2. D10-29 04:36PM 12.953
> >
> >plugins - trying commonplugs.forward
> >
> >3. E10-29 04:36PM 50.560
> >
> >:
> >Traceback (most recent call last):
> >
> > Its all deadline errors, notice the time difference between the last
> debug
> > line and the exception .. 38 seconds ??
> >
> > I dont use django but my own framework is getting huge and loading that
> > might be a problem. Real problem is though that i cant know for sure
> whether
> > its my code at fault or its appengine that has troubles. Its getting hard
> to
> > develop on a unstable platform ;[
> >
> > I suggest you do some serious logging in your app so you can see where
> >
> >
> >
> >
> >
> >
> >
> > > the time is taken up.  If its during initial imports
> > > then you may be in a pocket of poor performing appengine
> > > infrastructure at the moment.  (A few people seem to be having
> > > onoing problems since the 27th)  In addition  it will give you a
> > > better insight into how you app is behaving during startup.
> >
> > > It's also possible that you got a DeadLineExceeded during startup that
> > > has left you with a broken instance (this can happen if you using
> > > things
&

Re: [google-appengine] Early Christmas Present from Google?

[Bart Thate]

On Sat, Nov 6, 2010 at 11:17 PM, Greg  wrote:

> Check out the datastore stats after today's maintenance...
>
>
> http://code.google.com/status/appengine/detail/datastore/2010/11/06#ae-trust-detail-datastore-get-latency


I really really really hope it stays this way ;]
Latency dropped from 300 msec to 100msec for me

Bart
-- 
@jsonbot Heerhugowaard, Netherlands
programming schizofrenic - http://jsonbot.appspot.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-appeng...@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] troubles getting channels created

[Bart Thate]

Hello  appengine brother and sisters ;]

i wondered if any one is having problems getting channels created with the
new channel API. I got it working for my bot but now i have to wait several
minutes before the onopened callback is called. No activity on the channel
before this.

Anyone else seeing this or is this the usual borking on my side ?

Grtx,

Bart

@jsonbot Heerhugowaard, Netherlands
programming schizofrenic - http://jsonbot.appspot.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-appeng...@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] JSONBOT 0.5 RELEASED

[Bart Thate]

Hello world ;]

I'm back with another release of JSONBOT, this time it is version 0.5
so we are half way through making this a 1.0 release. Lot of changes
to the core as well as other bug fixes, let me sum it up:

* this version requires an upgrade of your 0.4 JSONBOT if you run
already a JSONBOT see UPGRADE for more details on this.
* code is adapted to use the Channel API, you need google_appengine
version 1.4.0 for this.
* website has gotten a brand new look and feel.
* JSONBOT now uses ~/.jsonbot as its default datadir.
* the RSS plugin was rewritten to work on any feed instead of only
feed that support the pubDate token.
* shell bots now log to ~/.jsonbot/botlogs by default, rotating the
logs every day.
* lots and lots of bug fixes.

pointers:

* source code: http://jsonbot.googlecode.com
* web demo: http://jsonbot.appspot.com
* jabber demo: json...@appspot.com
* documentation: http://jsonbot.appspot.com/docs
* bugs: http://code.google.com/p/jsonbot/issues/list
* twitter: http://twitter.com/#!jsonbot

I consider JSONBOT to be of BETA quality now, i think it has become
quite usable ;] Any feedback would be very much appreciated.

As always ... HF !

Bart

about JSONBOT:

JSONBOT is a remote event-driven framework for building bots that talk
JSON to each other over XMPP.

This distribution provides bots built on this framework for console,
IRC, XMPP for the shell and WWW and XMPP for the Google Application
engine.

JSONBOT is all of the following:

* a shell console bot
* a shell IRC bot
* a shell XMPP bot
* a Web bot running on Google Application Engine
* a XMPP bot running on Google Application Engine
* a Google Wave bot running op Google Application Engine
* the XMPP bots are used to communicate between bots
* plugin infrastructure to write your own functionality
* event driven framework by the use of callbacks

-- 
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-appeng...@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] Channel API CPU usage

[Bart Thate]

Hoi Andy,

these times are normal and can take upto 10 seconds i read. Normal for me is
3 seconds.

@jsonbot Heerhugowaard, Netherlands
programming schizofrenic - http://jsonbot.appspot.com

On Sat, Dec 11, 2010 at 1:37 AM, Andy Kim  wrote:

> The new Channel API is awesome and it opens up many possibilities on what I
> can do with GAE. I have noticed however, that creating a channel takes about
> 2800 ms of API CPU time. Is everyone else seeing similar times or am I doing
> something wrong 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-appeng...@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-appeng...@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] JSONBOT 0.6 RELEASED

[Bart Thate]

Hello world and the best wishes for 2011 for all of you !

i'm pleased to announce version 0.6 of JSONBOT, a release that saw it's
complete codebase refactored. Things have moved into their own package,
making it easier to distribute JSONBOT to the various OS around. I even
renamed the name of the distribution to "jsb", so use the jsb-0.6.tar.gz or
"easy_install jsb" to get this version of JSONBOT.

So once again i need to ask existing users to upgrade their JSONBOT install,
see http://jsonbot.appspot.com/docs/html/handbook/UPGRADE.html for
instructions on how to do that.

Functionality of the bot is the same as 0.5.

For more information on JSONBOT, see http://jsonbot.googlecode.com or join
us on #dunkbots Freenode.
Bot documentation and demo is on http://jsonbot.appspot.com
I hope you enjoy this release of JSONBOT, i'm glad i can start working on
0.7 ;]

About JSONBOT:

JSONBOT is a remote event-driven framework for building bots that talk JSON
to each other over XMPP.

This distribution provides bots built on this framework for console, IRC,
XMPP for the shell and WWW and XMPP for the Google Application engine.

JSONBOT is all of the following:

* a shell console bot
* a shell IRC bot
* a shell XMPP bot
* a Web bot running on Google Application Engine
* a XMPP bot running on Google Application Engine
* a Google Wave bot running op Google Application Engine
* the XMPP bots are used to communicate between bots
* plugin infrastructure to write your own functionality
* event driven framework by the use of callbacks

Bart

@jsonbot Heerhugowaard, Netherlands
programming schizofrenic - http://jsonbot.appspot.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-appeng...@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] JSONBOT 0.6.1 RELEASED

[Bart Thate]

Hello every human out there !

i'm pleased to announce the release of JSONBOT 0.6.1 FINAL, a release
that saw a lot of work into the shell side of things and no changes to
GAE.

0.6.1 has the following changes:

* the ! char is not used instead of | in a pipeline. This is to make
it easier to use a pipeline on mobile phones.

* a new commandline interface has been created. You can now do "jsb
botcommand " .. no need to start up the console app when you have a
single command to execute

* ? is now used a query character, so things you learn the bot with !
learn can be queried with ?

* auto_register and guestasuser config options are now disabled by
default

* core xmpp parsing code has been rewritten

* many more bug fixes.

You can grab a copy of the code (tarball or mercurial repo) at
http://jsonbot.googlecode.com

Hope you enjoy this release as much as i enjoyed making it ;]
Have Fun !

Bart

About JSONBOT:

JSONBOT is a remote event-driven framework for building bots that talk
JSON to each other over XMPP.

This distribution provides bots built on this framework for console,
IRC, XMPP for the shell and WWW and XMPP for the Google Application
engine.

JSONBOT is all of the following:

a shell console bot
a shell IRC bot
a shell XMPP bot
a Web bot running on Google Application Engine
a XMPP bot running on Google Application Engine
a Google Wave bot running op Google Application Engine
the XMPP bots are used to communicate between bots
plugin infrastructure to write your own functionality
event driven framework by the use of callbacks

-- 
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] Twitter + OAuth Python example

[Bart Thate]

Try tweepy, its really nicely written.

http://joshthecoder.github.com/tweepy/docs/auth_tutorial.html#oauth-authentication


Groet,

Bart

@jsonbot Heerhugowaard, Netherlands
programming schizofrenic - http://jsonbot.appspot.com



On Sun, Mar 20, 2011 at 10:37 PM, Raisen  wrote:

> I've searched for awhile but couldn't find a recent working example to
> integrate Twitter + OAuth on Google App Engine using Python. I've
> tried this class
>
> http://code.google.com/p/oauth-python-twitter2/
>
> but I wasn't able to make it to work on App Engine.
>
> --
> 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] Re: Prerelease SDK 1.4.3 now available for download

[Bart Thate]

great scoop ! ;]

looking forward to use sqlite as well as i can port between shell and gae
better.

Bart

@jsonbot Heerhugowaard, Netherlands
programming schizofrenic - http://jsonbot.appspot.com



On Fri, Mar 25, 2011 at 11:25 PM, Tobias wrote:

> Hi Ikai,
>
> After digging through the prerelease (Python), I've discovered a couple of
> very promising new modules regarding rdbms support:
>
> google_appengine/google/appengine/api/rdbms.py
> google_appengine/google/appengine/api/rdbms_mysqldb.py
> google_appengine/google/appengine/api/rdbms_sqlite.py
> google_appengine/google/storage/speckle/python/api/rdbms.py
>
> So, I've made a tiny demo app to try it out.
>
> http://github.com/rodaebel/simplenotes - Works like a charm with SQLite :)
>
> Since the prerelease notes don't mention this stuff, I guess it's
> experimental and we're likely not going to see rdbms support in the upcoming
> 1.4.3 release. Anyway, congratulations for this awesome prerelease. I'm
> eager for the next updates!
>
> - Tobias
>
> --
> 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] JSONBOT 0.7 RELEASED

[Bart Thate]

0.7 RELEASE NOTES
=

Hello world, greetings to all and everybody on this little planet ;]

Today I am releasing version 0.7 of JSONBOT, hope you like it.

I want to dedicate this release to Annemiek, Kirsten, Danny and
Doscha, i would not have a live without you.

changes in this release
---

* we got jsonbot.org running .. see http://jsonbot.org ;]
* convore support
* refactored core
* reloadable config files
* revamped web console
* resource files (contain commands the bot can execute)
* file change detection for myplugs plugins
* rebooting is fixed
* fixed relaying in jabber conference rooms
* added color.py plugin to color certain words
* added geo.py, googletranslate.py and imdb.py (thnx melmoth)
* chatlog plugin now uses the logging module .. log file rotates every
day
* many other bugfixes

If you have programmed your own plugin see
http://jsonbot.org/handbook/UPGRADE.html for upgrade notes.

Todo


1) fix runtime setting of loglevel
2) add flood control
3) docs docs docs docs docs
4) fix bugs

see http://code.google.com/p/jsonbot/issues/list

Source
--

* tarball - http://jsonbot.googlecode.com
* mercurial - http://jsonbot.googlecode.com/hg
* github - https://github.com/jsonbot

Demo


* webconsole - http://jsonbot.appspot.com
* xmpp - json...@jsonbot.org (shell) and json...@appspot.com (GAE)
* IRC - jsonbot on irc.freenode.net
* Convore - https://convore.com/convore-8/welcome-to-convore/ relaying
with #convore on irc.freenode.net

Docs


* new jsonbot.org site .. http://jsonbot.org
* GAE backup docs .. http://jsonbot.appspot.com/docs

Contact
---

* twitter: https://twitter.com/#!/jsonbot
* facebook: http://tinyurl.com/jsonbot
* email: bth...@gmail.com
* IRC: dunker in channel #dunkbots / irc.freenode.net* xmpp:
bth...@gmail.com and b...@jsonbot.org

About
-

JSONBOT is a remote event-driven framework for building bots that talk
JSON
to each other over XMPP.

This distribution provides bots built on this framework for console,
IRC,
XMPP and Convore for the shell and WWW and XMPP for the Google
Application engine.

JSONBOT is all of the following:

* a shell console bot
* a shell IRC bot
* a shell XMPP bot
* a shell Convore bot
* a Web bot running on Google Application Engine
* a XMPP bot running on Google Application Engine
* a Google Wave bot running op Google Application Engine
* the XMPP bots are used to communicate between bots
* plugin infrastructure to write your own functionality
* event driven framework by the use of callbacks

Install
---

You dont need to run the bot on GAE when you just want to use the
shell bots of JSONBOT. JSONBOT can best be run from the bot dir, the
bot is self contained and has all the dependancies that are needed:

* "hg clone http://jsonbot.googlecode.com/hg mybot" or download and
untar the tarball.
* cd into the bot dir and run "./bin/jsb" .. if the bot is working
correctly you will get the console version of JSONBOT
* same can be done for "./bin/jsb-xmpp", "./bin/jsb-convore" etc. ..
check the bin dir for programs you can start
* try the --help option to a program to see what command line options
are available.
* you DONT need root for this

Ofcourse you can always run "python setup.py install" or "easy_install
-U jsb" when you do want to install the bot globaly.
Debian packages are on their way, but might still take time as the
ftpmeisters need to approve ;]

Thats it ! hope you enjoy this version of JSONBOT ;]

Bart

-- 
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] The memory tax

[Bart Thate]

Greetings !

As i understand it this whole move of Google is because they discovered that
it is the memory occupied thats is the cost factor requiring this drastic
move. So if that is the case why not introduce a new billable entitiy
"memory" ? That way users can still get their bill for what they use and it
gives us programmers the incentive to be sparefull with such a costly
attribute of GAE.
My feeling is that this "we will make the scheduler work ok for you"
argument is not going to work as the question is how will Google make the
working of this scheduler clear to us users ? I never had the feeling Google
is open about how they do things and i don't think Google will open up the
exact workings of this piece of key software.

Why not keep what is running fine and add the "memory tax" on top of it.

Billing needs to be clear and verifiyable otherwise this move will not work.

Bart

@jsonbot Heerhugowaard, Netherlands
programming schizofrenic - http://jsonbot.appspot.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] Re: The memory tax

[Bart Thate]

Oi Robert ;]

responses below

@jsonbot Heerhugowaard, Netherlands
programming schizofrenic - http://jsonbot.appspot.com



On Wed, Jun 1, 2011 at 6:45 AM, Robert Kluin  wrote:

> There have been one or two other threads where this has been suggested
> as well.  I originally had a similar thought, but after some thought I
> honestly think it sounds very complicated, you'll have both CPU hours
> and memory-meg-hours (or whatever).
>
>
Google already measures your app memory use:


Charts [image: help]<http://code.google.com/appengine/kb/general.html#charts>
Requests/SecondRequests by Type/SecondMilliseconds/RequestErrors/SecondBytes
Received/SecondBytes Sent/SecondCPU Seconds Used/SecondMilliseconds
Used/SecondNumber of Quota Denials/SecondInstancesMemory Usage (MB)
6 hrs
12 hrs
24 hrs
2 days
4 days
7 days
14 days
30 days
[image: Requests/Second (24 hrs)]

I'm glad im below the 128 Mb limit ;]


> I sometimes see much higher memory usage than expected, and we've got
> no tools to debug this on production.  It would probably just add
> another area of 'discussion' and questioning.
>
>
Once memory is billable, you gonna be sure that people actually try to make
good use of it. If you do instance price only who cares ?
As for debugging you might have point maybe google could provide the an app
stats API where the app could monitor its memory usage itself (or is there
already such a API) ?

Bart


> On Tue, May 31, 2011 at 23:56, JH  wrote:
> > I'd prefer this over the instance billing as well
> >
> > On May 31, 8:36 pm, Bart Thate  wrote:
> >> Greetings !
> >>
> >> As i understand it this whole move of Google is because they discovered
> that
> >> it is the memory occupied thats is the cost factor requiring this
> drastic
> >> move. So if that is the case why not introduce a new billable entitiy
> >> "memory" ? That way users can still get their bill for what they use and
> it
> >> gives us programmers the incentive to be sparefull with such a costly
> >> attribute of GAE.
> >> My feeling is that this "we will make the scheduler work ok for you"
> >> argument is not going to work as the question is how will Google make
> the
> >> working of this scheduler clear to us users ? I never had the feeling
> Google
> >> is open about how they do things and i don't think Google will open up
> the
> >> exact workings of this piece of key software.
> >>
> >> Why not keep what is running fine and add the "memory tax" on top of it.
> >>
> >> Billing needs to be clear and verifiyable otherwise this move will not
> work.
> >>
> >> Bart
> >>
> >> @jsonbot Heerhugowaard, Netherlands
> >> programming schizofrenic -http://jsonbot.appspot.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.
> >
> >
>
> --
> 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] JSONBOT 0.7.1 released

[Bart Thate]

Hello kids and parents !! I just want to announce the release of
JSONBOT 0.7.1.

This release consists of minor bug fixes and new xmpp auth code (SASL)
which support DIGEST-MD5 and PLAIN authing.

JSONBOT should run well again on systems with python2.5 installed.

You can fetch it at http://jsonbot.googlecode.com

Have fun playing with it!

Bart

About JSONBOT:

JSONBOT is a remote event-driven framework for building bots that talk
JSON
to each other over XMPP.

This distribution provides bots built on this framework for console,
IRC,
XMPP and Convore for the shell and WWW and XMPP for the Google
Application engine.

JSONBOT is all of the following:

* a shell console bot
* a shell IRC bot
* a shell XMPP bot
* a shell Convore bot
* a Web bot running on Google Application Engine
* a XMPP bot running on Google Application Engine
* a Google Wave bot running op Google Application Engine
* the XMPP bots are used to communicate between bots
* plugin infrastructure to write your own functionality
* event driven framework by the use of callbacks

-- 
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: Updated App Engine Pricing FAQ!

[Bart Thate]

On Mon, Jun 27, 2011 at 6:44 PM, vivpuri  wrote:

And out here we have Google, where in 3 years of going live with the
> product, we are seeing paradigm shift in pricing. And this shift has
> come as a total disregard for the application developers time, effort
> and contribution to the platform. Existing developers with really
> large applications are being forced(without alternative option) down a
> path that is unknown, while existing issues have not been resolved and
> features asked for years back not delivered. Personally i dont even
> have time and energy to understand all the new jargon that has been
> thrown out there.


Hear hear ! Developer costs are not calculated into the new pricing.

"forced on a unknown path"

Bart

 programming schizofrenic - http://tinyurl.com/jsonbot
@jsonbot Heerhugowaard, Netherlands

-- 
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: Need help understanding Appengine billing

[Bart Thate]

Hoi Kwame,

sample billing in which you can see what your app is going to cost in the
new billing system is going to be here "soon", see the IRC chat log for more
information about that.

Greetings,

Bart

programming schizofrenic -  http://tinyurl.com/bart-thate




On Thu, Jul 21, 2011 at 2:01 PM, Kwame  wrote:

> Thanks Johan,
>
> I see your billing scheme, and I can sort of understand what the
> different terms mean, but it is difficult to wrap my brain around what
> the costs actually end up being in a real website. It would be helpful
> to get some examples of what other people have actually paid, and what
> kind of usage they have. I just need to make some rough estimates, so
> any examples will do.
>
>
>
> On Jul 21, 7:50 am, Johan Euphrosine  wrote:
> > Hi Kwame,
> >
> > The current billing documentation is here:
> http://code.google.com/appengine/docs/billing.html
> >
> > However later this year we will introduce a new billing scheme which
> > is described here:
> http://www.google.com/enterprise/cloud/appengine/pricing.html
> >
> > Community members that are willing to share metrics about their QPS,
> > current quota usage and billing are more than welcome to comment to
> > this threads.
> >
> > Hope that helps.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On Thu, Jul 21, 2011 at 6:55 AM, Kwame  wrote:
> > > I've been using Appengine for a while, and I haven't yet exhausted my
> > > free quota. I'm running a business and I would need to set a budget
> > > for my server costs. I'm not able to understand how the billing units
> > > like CPU Time, Outgoing Bandwidth, Incoming Bandwidth & Total Stored
> > > data apply in real world usage of a typical busy website. Can anyone
> > > give me some sample charges for a typical website and approximately
> > > how much of these resources can be expected to be consumed, so I can
> > > compare with my site to get an approximate estimate.
> >
> > > 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 athttp://
> groups.google.com/group/google-appengine?hl=en.
> >
> > --
> > Johan Euphrosine (proppy)
> > Developer Programs Engineer
> > Google Developer Relations
>
> --
> 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] Sqlite3 for backends

[Bart Thate]

Oi !

Agree completely, in fact really forgot about it ;]
I thought it was on the roadmap, not sure though .. maybe 2.7 supports
sqlite as the python module is already builtin ?
Hmm just checked the roadmap and only 2.7 support is on it, lets hope they
dont exclude "import sqlite3" from the deal.

Bart

programming schizofrenic -  http://tinyurl.com/bart-thate




On Mon, Sep 12, 2011 at 4:07 PM, Andrin von Rechenberg
wrote:

> Hi there
>
> Is there any plan to support the sqlite3 module in python in GAE?
> It would be very useful if someone would want to build an SQL like backend.
>
> -Andrin
>
> --
> 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] public, dynamic backends are magical (in a good way!!)

[Bart Thate]

I wish i could +1 on postings like this ! Gonna try it out tomorrow ;]
Thnx.

Bart Thate

programming schizofrenic - "till freedom come!"

[!] http://protocol.by/botfather
[!] http://botfather.blogspot.com
[!] http://jsonbot.org



On Sat, Sep 24, 2011 at 8:23 PM, Adam Sah  wrote:

> hey guys--
>
> If you're using Tasks and haven't tried public, dynamic Backends yet,
> they're wonderful:
>  - for tiny apps, you can offload another $0.72/day for free (they're
> dynamic!)
>  - for medium apps, it's a super easy way to get more RAM
>  - easy migration from Tasks running on frontends to running them on
> public, dynamic backends (incl development, debugging, etc.)
>  - nearly identical debugging/production methods as frontend Tasks
>  - since they're public, you can launch Tasks directly on the backend,
> removing the frontend from the equation, e.g. you can test out how a
> Task will perform on a backend, before committing to the architecture
> change.
>  - cool trick: keep the fast Tasks running on frontends, and use the
> (expensive) backends for RAM-intensive jobs-- this is a tiny code
> change, and also makes it easier to debug large jobs because the
> console isn't flooded with little jobs.  For my app, I use Tasks for
> various indexing jobs in an online marketplace-- now, I send the
> "large" sellers with 1000s of SKUs, to a B4 backend.
>
> GAE team:
>  - I've noticed that my backends can 500-error but not produce a stack
> trace in the logs?  are other people seeing this?
>
> my choice of migration: (python)
>
> 1. create backends.xml, define *one* backend, e.g.
>backends:
> - name: backend2647324# since it's public, give it a hard-to-
> guess name
>   class: B4# big+fast without blowing the free budget
>   options: dynamic, public
>
> 2. add backend-enabled queued, by copying queues from frontends:
>
>   queue:
>- name: image-processor
>  ...other options here...
>
>- name: image-processor-backend # note how I append "-backend"
> to the name
>  target: backend2647324
>  ...other options here...
>
> 3. in your code, start firing Tasks at the backend
>
># see bottom for taskname() trick
>taskqueue.add(url=..., name=taskname("some-identifier-i-will-
> recognize"),
>queue_name="image-thumbnailer"+("-backend" if
> is_gigantic_image(...) else ""))
>
> 4. modify your deploy script to update both the front & backends.
> Mine (legacy) is in perl:
>
> # deploy bar   ==> deploys to foo-bar and to foo-bar-backend
> # deploy bar-backend   ==> deploys to foo-bar-backend only
> # deploy bar-frontend   ==> deploys to foo-bar only
> $DEST = pop(@ARGV);
> my $push_frontend = 1;
> if ($DEST =~ s/-backend//) { $push_frontend = 0; }
> my $push_backend = 1;
> if ($DEST =~ s/-frontend//) { $push_backend = 0; }
> if ($push_frontend) {
>  open(FH, "echo ".$ENV{"GAEPASSWD"}."|python2.5 ".$ENV{"GAEDIR"}."/
> appcfg.py --email=".$ENV{"GAEUSER"}." --passin --application=foo-$DEST
> update .|");
>  while () { print; }
>  close FH;
> }
> if ($push_backend) {
>  open(FH, "echo ".$ENV{"GAEPASSWD"}."|python2.5 ".$ENV{"GAEDIR"}."/
> appcfg.py --email=".$ENV{"GAEUSER"}." --passin --application=foo-$DEST
> backends . update|");
>  while () { print; }
>  close FH;
> }
>
>
> that's it!  now, some jobs will go to the frontends and others to the
> backends.
>
> hope this helps,
> adam
>
>
> def taskname(string):
>  """safely create Google App Engine Task names."""
>  # add timestamp and random for ultimate uniqueness, strip disallowed
> chars
>  rnd_salt = str(random.randint(10, 99))
>  return re.sub(r'[^a-zA-Z0-9-]', '-', string +
> str(datetime.datetime.now())) + "-" + rnd_salt
>
> --
> 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] New Channel API pricing scheme

[Bart Thate]

big time ;[

Bart Thate

programming schizofrenic - "till freedom come!"

[!] http://protocol.by/botfather
[!] http://botfather.blogspot.com
[!] http://jsonbot.org



On Thu, Oct 20, 2011 at 4:28 PM, Chiguireitor
wrote:

> 100 creations/day yeah... sucks
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/_vbzAm_bxlcJ.
> 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] Twitter Library

[Bart Thate]

I am using tweepy, see http://code.google.com/p/tweepy/
It is clean code, like it a lot ;]

Bart Thate

programming schizofrenic - "till freedom come!"

[!] http://protocol.by/botfather
[!] http://botfather.blogspot.com
[!] http://jsonbot.org



On Thu, Nov 10, 2011 at 11:38 AM, Max wrote:

> Hi,
> I want to develop a Twitter client in Appengine and I have seen that there
> are many libraries developed.
> Which is the best? Feedback? (Please advice where I can find the
> documentation of the library).
> I'm for twython, but I can't find documentation on how to use it in
> Appengine.
>
> Thanks
>
> Max
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/VoKFCnRMhBYJ.
> 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] JSONBOT 0.80.3 released

[Bart Thate]

Hello world !! I released JSONBOT 0.80.3 .. the first in the 0.80 series ;] 

about 
~ 

JSONBOT is a chatbot that can take commands and react to events on the 
network it is connected to (IRC, XMPP, WEB 
mostely). Push functionality is also provided (think RSS feeds to your IRC 
channel or XMPP conference). It is possible to program your own plugins to 
create custom 
functionality. 

source/docs 
~~~ 

 see http://jsonbot.org and http://jsonbot.googlecode.com 


make backup first 
~ 

I added the jsb-backup program, please run this before starting the 0.80 
bot. It will make a backup of your datadir into ~/jsb-backups 

changes 
~~~ 

* GAE is no longer part of the standard distribution, as that is aimed at 
shell users as of 0.80 - use the mercurial repo if you want to use the GAE 
part of the bot 
* web console is now supported on shell - use the jsb-tornado program to 
launch a tornado web server bot on port 10102 
* jsb-xmpp now supports OpenFire - use --openfire option to enable this 
* todo now uses per user databases instead of per channel - use the -c 
option to the todo command to show the channel todo 
* learn items are not global per default - use !learn-toglobal to copy 
local learn data to the global learndb 
* relay plugins has been rewritten to use bot.cfg.name as well - means that 
relays need to be created again   
* jsb-udpstripped program has been added that can be used to send udp data 
to the bot without the need of making config files (copy and edit it) 
* add fulljids = 1 to your xmpp bot config (most of the times in 
~/.jsb/config/fleet/default-sxmpp/config) to enable full JID discovery in 
xmpp conference rooms 
  (non anonymous) 

and: 

* lots of new plugins .. see !list ;] 
* lots of bug fixes - thnx everybody for reporting them 
* still lots of things to fix at 

03:35 < jsonbot> tracker is http://code.google.com/p/jsonbot/issues/list 

If you find any problems or have feature request please post that on the 
tracker url above. 

Or try @botfather on #dunkbots on irc.freenode.net ;] 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/K9SWy1WvFTgJ.
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: Isn't .08/hr 1.92/day $59.52/month for a 600 MHZ CPU instance with 128 MB memory a LITTLE EXPENSIVE

[Bart Thate]

On Thu, Dec 15, 2011 at 12:55 AM, mike hershey wrote:

I think most people who use app engine prefer it because you don't have to
> understand how everything works. I get a black box servlet environment,
> datastore, and whatever else a site typically needs. I don't have to waste
> time knowing how all of this works, I just get to use it. People who need
> the sort of control you are talking about tend to prefer IaaS services
> where you can control how everything works.
>

You said the magic word .. "black box". In all these ramblings i never see
the costs for the developers calculated in. GAE might be heaven for admins
that dont want todo the dirty work themselves, for me GAE is a hell because
i don't have any control over the runtime enironment at all. If something
is not working i can't check logs, i have to buy a 500 dollar a month
package to get some support from Google to go look what is going wrong.
Nothing worse then having your app misbehave, shout something in the IRC
channel and after some time, heee its fixed ! Gives me no clue of whats
going on and just that is so important for me when i develop things.

The other thing that connects to the developers costs thing i have against
GAE and more against Google is the use of API. These API get deprecated
quicker then i can start reading their docs, and when they get into
"mainstream" i have to fork over money to use them. As i write software for
other people to use, that would require them to make use of this *paid* API
so i can never build upon them in the core of my app. Sure i  can make a
plugin for this API and make it optional, but say like integrating the
translation API into my bot (would be extreeemly usefull) is a nono. We
need FOA .. Free and Open API, things i can rely on. Not so with Google
though.

Last thing is that Google choose the evil path, it has killed the hippie
amongst all of us programmers. The vibrant community that was created with
Wave has also disappeared with the death of it. Is the HRD the holy grail
of cloud computing (only reason i would use GAE i think), it is there
because so many of us went down the rough road on M/S in those early days.
Now i feel the spirit is lost and people are only choosing GAE because they
have already so much invested in it (developer wise).

I miss the socket on GAE, really do. Programming with sockets is so much
better because you get "pure" internet not just HTTP and streaming is
possible. Streaming people ! Stream it ;]

Bart Thate

programming schizophrenic - "till freedom come!"

[!] http://jsonbot.org
[!] http://tinyurl.com/schizoo

-- 
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: Google App Engine community support is moving to Stack Overflow

[Bart Thate]

If you are on IRC freenode i just made a channel where my bot spams the RSS
feed of stackoverflow. Channel is #appengine-overflow ;]

On Tue, Feb 7, 2012 at 4:27 PM, Andrin von Rechenberg wrote:

> My main concern is that I will miss many of the questions & answers,
> because I will have to manually go an check StackOverflow.
>
> Is there a way to get a daily StackOverflow digest email?
>
> Cheers,
> -Andrin
>
>
> --
Bart Thate

programming schizophrenic - "till freedom come!"

[!] http://jsonbot.org
[!] http:// <http://tinyurl.com/schizoo>gozerbot.org
[!] http://tinyurl.com/schizoo

-- 
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] Error code 203

[Bart Thate]

   
   1. 
   Hi GAE crew !
   1. 
  2. 012-03-08 11:43:35.845 /dispatch 500 100064ms 0kb Mozilla/5.0 
  (X11; Linux x86_64) AppleWebKit/535.11 (KHTML, like Gecko) Ubuntu/12.04 
  Chromium/17.0.963.66 Chrome/17.0.963.66 Safari/535.11
  
   - - [08/Mar/2012:02:43:35 -0800] "POST /dispatch HTTP/1.1" 500 108 
- "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.11 (KHTML, like Gecko) 
Ubuntu/12.04 Chromium/17.0.963.66 Chrome/17.0.963.66 Safari/535.11" 
"jsonbot-dev.appspot.com" ms=100065 cpu_ms=3800 api_cpu_ms=300 cpm_usd=0.105758 
exit_code=203 instance=00c61b117cbd9e17c4e23db6450f4ab1d63a40 

  
  3. I2012-03-08 11:43:35.836
  
  The process handling this request unexpectedly died. This is likely to 
cause a new process to be used for the next request to your application. (Error 
code 203)
  
  
  
   
   I get this error when trying to create a channel on my bot. Appid is 
   jsonbot-dev, python2.7, threadsafe is true, rebooting the instance makes no 
   difference.
   App is not dead, i handles cron calls properly, even booting the bot 
   works ok.
   Just when i try to open the frontpage, that does a XHR to create a 
   channel token this is what i get.
   
   No logs no nothing .. can't diagnose any other way then black box 
   guessing what is going on ;[
   Without threadsafe enabled the thing "just works", see 
   https://jsonbot-hr.appspot.com
   
   Any one can diagnose this ?
   
   Thnx,
   
   Bart
   *
   *
   

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/3pxpln0RLfQJ.
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: Error code 203

[Bart Thate]

So how can i diagnose what the reason is ?


On Thu, Mar 8, 2012 at 12:19 PM, Anand Mistry  wrote:

> For some reason, your request is exceeding the request deadline. Note how
> ms=100065 > 60 seconds.
>
>
> On Thursday, 8 March 2012 21:53:00 UTC+11, Bart Thate wrote:
>>
>>
>>1.
>>Hi GAE crew !
>>1.
>>   2. 012-03-08 11:43:35.845 /dispatch 500 100**064ms 0kb Mozilla/5.0
>>   (X11; Linux x86_64) AppleWebKit/535.11 (KHTML, like Gecko) Ubuntu/12.04
>>   Chromium/17.0.963.66 Chrome/17.0.963.66 Safari/535.11
>>
>>- - [08/Mar/2012:02:43:35 -0800] "POST /dispatch HTTP/1.1" 500 
>> 108 - "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.11 (KHTML, like 
>> Gecko) Ubuntu/12.04 Chromium/17.0.963.66 Chrome/17.0.963.66 Safari/535.11" 
>> "jsonbot-dev.appspot.com" ms=100065 cpu_ms=3800 api_cpu_ms=300 
>> cpm_usd=0.105758 exit_code=203 
>> instance=00c61b117cbd9e17c4e23**db6450f4ab1d63a40 
>> <https://appengine.google.com/instances?app_id=s~jsonbot-dev&version_id=2.357035453348805392&key=00c61b117cbd9e17c4e23db6450f4ab1d63a40#00c61b117cbd9e17c4e23db6450f4ab1d63a40>
>>
>>   3. I2012-03-08 11:43:35.836
>>
>>   The process handling this request unexpectedly died. This is likely to 
>> cause a new process to be used for the next request to your application. 
>> (Error code 203)
>>
>>
>>
>>
>>I get this error when trying to create a channel on my bot. Appid is
>>jsonbot-dev, python2.7, threadsafe is true, rebooting the instance makes 
>> no
>>difference.
>>App is not dead, i handles cron calls properly, even booting the bot
>>works ok.
>>Just when i try to open the frontpage, that does a XHR to create a
>>channel token this is what i get.
>>
>>No logs no nothing .. can't diagnose any other way then black box
>>guessing what is going on ;[
>>Without threadsafe enabled the thing "just works", see
>>https://jsonbot-hr.appspot.com
>>
>>Any one can diagnose this ?
>>
>>Thnx,
>>
>>Bart
>>*
>>*
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/Tro_9l2chs0J.
>
> 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.
>



-- 
Bart Thate

programming schizophrenic - "till freedom come!"

[!] http://jsonbot.org
[!] http:// <http://tinyurl.com/schizoo>gozerbot.org
[!] http://tinyurl.com/schizoo

-- 
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] So how do i unsubscribe to GAE ?

[Bart Thate]

I disabled all my apps, anything i need todo to get my appengine part of my
account disabled ?


-- 
Bart Thate

programming schizophrenic - "till freedom come!"

[!] http://jsonbot.org
[!] http:// <http://tinyurl.com/schizoo>gozerbot.org

-- 
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.