[google-appengine] Re: Forward request or webapp.RequestHandler chaining (like Actions framework in java)

2009-03-17 Thread Serega.Sheypak
Yes, Java made my mind tooo complicated. You've written clear solution: invoke one handler from another. That is why I've immediately started to learn Python+ GAE (wow), Ruby +RoR (awesome! cool!) and Lisp(brain blast) . Java made my mind Javable... :( On Mar 16, 12:44 am, Jarek Zgoda

[google-appengine] Re: Forward request or webapp.RequestHandler chaining (like Actions framework in java)

2009-03-16 Thread xml2jsonp
Yes, ok. You could open a New Issue... On Mar 15, 10:44 pm, Jarek Zgoda jarek.zg...@gmail.com wrote: It would be easier if you do not use WebApp but follow Django way of request handling (easy to achieve even without Django, ie. using Werkzeug to lay out application in model-view-template

[google-appengine] Re: Forward request or webapp.RequestHandler chaining (like Actions framework in java)

2009-03-15 Thread xml2jsonp
Why have the Java developers a complex mind? I think this is more simple: values = {'message':'News was hidden'} # self.redirect(/admin) path = os.path.join(os.path.dirname(__file__),'html/admin.html') self.response.out.write( template.render(path, values) ) . . . On Mar 15, 12:06 pm,

[google-appengine] Re: Forward request or webapp.RequestHandler chaining (like Actions framework in java)

2009-03-15 Thread Jarek Zgoda
It would be easier if you do not use WebApp but follow Django way of request handling (easy to achieve even without Django, ie. using Werkzeug to lay out application in model-view-template style): def handler_a(request): return response('a') def handler_b(request): return handler_a(request)