Mailman 3 January 2005 - Twisted-web

Re: [Twisted-web] livepage breaks after reload
by noema Jan. 26, 2005

Jan. 26, 2005

> In weever (http://vercingetorix.dyndns.org:20080) I use liveevil > with nevow from svn and it only breaks with safari. Your app seems to work on my browsers > I think you are probably using an old version of nevow or > something like that. I just svn'd nevow the other day and to make sure I checked out the most current version again today -> the problem persists. > otherwise you are probably doing something > wrong with the code but it's hard to tell without any code. OK ... I boiled down my code to the bare minimum (originally it is derived from the chatola app) and as i suspected the problem is still reproducable. The following is a .tac file which I start with "twistd -noy <filename>". It starts a server with one page that has two livepage handlers. One of them is called when the page loads another one when you click the link. Everything works fine until I reload the page and/or add some locateChild action. More constructive thoughts appreciated. _noema #################### START OF .TAC FILE ######################## import random from twisted.cred import portal, checkers, credentials from twisted.application import service, internet from nevow import inevow, loaders, rend, tags from nevow import livepage, guard, url, appserver class MyPageRealm: __implements__ = portal.IRealm def __init__(self): self.clients = [] self.topic = "test1" def requestAvatar(self, avatarId, mind, *interfaces): if inevow.IResource in interfaces: if avatarId is checkers.ANONYMOUS: mind.userId = random.choice(('one', 'two', 'three')) def onSessionExpire(): self.userLeft(mind) return (inevow.IResource, MyPage([self, mind]), onSessionExpire) raise NotImplementedError("Can't support that interface.") def userJoined(self, client): if client in self.clients: self.userLeft(client) self.clients.append(client) def userLeft(self, client): self.clients.remove(client) class MyPage(rend.Page): def __init__(self, data): rend.Page.__init__(self, data) self.realm = data[0] self.client = data[1] def render_body(self, ctx, data): self.realm.userJoined(self.client) self.client.set('sometext', tags.h1['This is from LivePage!']) session = inevow.ISession(ctx) def unload(client): session.expire() return ctx.tag(onunload=livepage.handler(unload)) def onLinkAction(self, client): client.set('atag', random.choice(('one', 'two', 'three', 'four', 'five'))) def render_link(self, context, data): return tags.a(onclick=livepage.handler(self.onLinkAction), href=url.here, id="atag")['click!'] def render_glue(self, context, data): return livepage.glue docFactory = loaders.stan( tags.html[ tags.head[ tags.title["mypage"], ], tags.body(render=render_body)[ tags.div(id='sometext')['to be filled by livepage'], tags.div[ render_link ], tags.span(render=render_glue) ] ]) realm = MyPageRealm() portal = portal.Portal(realm) portal.registerChecker(checkers.AllowAnonymousAccess(), credentials.IAnonymous) site = appserver.NevowSite( guard.SessionWrapper(portal, mindFactory=livepage.LiveEvil)) application = service.Application("mypage") internet.TCPServer(8080, site).setServiceParent(application) #################### END OF .TAC FILE ##########################

1 0

livepage breaks after reload
by noema Jan. 25, 2005

Jan. 25, 2005

I have just started implementing another webapp, this time with livepage. When I tried to add more than one page objects (published objects derived from rend.Page) I noticed that any kind of page reload other than through JavaScript breakes the livepage functionality. When I tried to find the cause I did not get very far. It simply seems to me that python functions that are connected to javascript events do not get through. This does not only happen with my app but also with the chatola app from the example directory. When I reload chatola the browser does not update its html dom anymore. I basically have to restart the browser to make it work again. I can reproduce these symptoms on firefox 0.7-1.0 for linux and windows. I also noticed that the liveanimal example works fine throughout reloads. Constructive thoughts very much appreciated! #noema

1 0

livepage breaks after reload
by noema Jan. 25, 2005

Jan. 25, 2005

I have just started implementing another webapp, this time with livepage. When I tried to add more than one page objects (published objects derived from rend.Page) I noticed that any kind of page reload other than through JavaScript breakes the livepage functionality. When I tried to find the cause I did not get very far. It simply seems to me that python functions that are connected to javascript events do not get through. This does not only happen with my app but also with the chatola app from the example directory. When I reload chatola the browser does not update its html dom anymore. I basically have to restart the browser to make it work again. I can reproduce these symptoms on firefox 0.7-1.0 for linux and windows. I also noticed that the liveanimal example works fine throughout reloads. Constructive thoughts very much appreciated! #noema

1 0

Twisted web wiki has been attacked by spammers
by Mary Gardiner Jan. 24, 2005

Jan. 24, 2005

There's an awful lot of wikispam on the front page of http://divmod.org/users/wiki.twistd/nevow/moin.cgi ... it seems to have been there for at least a year. If the wiki is unmaintained it really should be taken down or frozen and made uneditable rather than letting it become a haven for spam links. -Mary

3 3

flattener for decimal type
by Andrea Arcangeli Jan. 24, 2005

Jan. 24, 2005

This avoids an exception when returning decimals through some data method. Works for me so far (apparently I didn't need to import the decimal module, not sure why ;). Index: nevow/__init__.py =================================================================== --- nevow/__init__.py (revision 1110) +++ nevow/__init__.py (working copy) @@ -209,6 +209,12 @@ """ +flatteners_2_4 = """ +nevow.flat.flatstan.StringCastSerializer decimal.Decimal +""" +if sys.version_info >= (2, 4): + flatteners += flatteners_2_4 + loadFlatteners(flatteners)

2 1

Re: [Nevow-commits] r1110 - Epydoc cleanup.
by James Y Knight Jan. 24, 2005

Jan. 24, 2005

Fixing the comments to look pretty in autogenerated docs seems like a good idea, but does epydoc *really* make you do the following?? There goes easy copy-and-pastability.. james > - def doSomething(self, context=formless.Context(), > name=formless.String()): > - pass > - doSomething = formless.autocallable(doSomething) > + >>> def doSomething(self, context=formless.Context(), > name=formless.String()): > + ... pass > + >>> doSomething = formless.autocallable(doSomething)

3 2

reduce deferred stack in nevow
by Andrea Arcangeli Jan. 22, 2005

Jan. 22, 2005

This is mostly a cleanup since I doubt you can measure any improvement unless you've tons of nested dirs to lookup. It's inefficient to use .addCallback().addErrback when addCallbacks could be used instead. Index: nevow/rend.py =================================================================== --- nevow/rend.py (revision 1092) +++ nevow/rend.py (working copy) @@ -511,11 +511,9 @@ return static.Data('You posted a form to %s' % bindingName, 'text/plain'), () return util.maybeDeferred( configurable.postForm, ctx, bindingName, args - ).addCallback( - self.onPostSuccess, request, ctx, bindingName, redirectAfterPost - ).addErrback( - self.onPostFailure, request, ctx, bindingName, redirectAfterPost - ) + ).addCallbacks(self.onPostSuccess, self.onPostFailure, + callbackArgs = (request, ctx, bindingName, redirectAfterPost), + errbackArgs = (request, ctx, bindingName, redirectAfterPost)) def onPostSuccess(self, result, request, ctx, bindingName, redirectAfterPost): if result is None: Index: nevow/appserver.py =================================================================== --- nevow/appserver.py (revision 1092) +++ nevow/appserver.py (working copy) @@ -147,21 +147,16 @@ return self.site.getPageContextForRequestContext( requestContext - ).addErrback( - processingFailed, self, requestContext - ).addCallback( - self.gotPageContext - ) + ).addCallbacks(self.gotPageContext, processingFailed, + errbackArgs = (self, requestContext)) def gotPageContext(self, pageContext): if pageContext is not errorMarker: return defer.maybeDeferred( pageContext.tag.renderHTTP, pageContext - ).addErrback( - processingFailed, self, pageContext - ).addCallback( - self._cbFinishRender, pageContext - ) + ).addCallbacks(self._cbFinishRender, processingFailed, + callbackArgs = (pageContext, ), + errbackArgs = (self, pageContext)) def finish(self): self.deferred.callback("") @@ -291,11 +286,9 @@ return defer.maybeDeferred( res.locateChild, ctx, path - ).addErrback( - processingFailed, request, ctx - ).addCallback( - self.handleSegment, request, path, ctx - ) + ).addCallbacks(self.handleSegment, processingFailed, + callbackArgs = (request, path, ctx), + errbackArgs = (request, ctx))

6 9

how create a dynamic pages using rpy scripts in twisted web
by Mosas Jan. 22, 2005

Jan. 22, 2005

Dear All, I want to know how to work with rpy extention having files and also how to create dynamic pages using rpy scripts. If any one having documentations or example scripts regarding this kindly mail me. I cannot get these things from net. regards prabahar ________________________________________________________________________ Yahoo! India Matrimony: Find your life partner online Go to: http://yahoo.shaadi.com/india-matrimony

1 0

Twisted, Nevow and The Meaning of Life
by ERGO Jan. 21, 2005

Jan. 21, 2005

Regardless of BIG respect and best regards to all developers of Twisted and Nevow a question: ... ... how far away is the next stable API ??? Paul Reznicek

2 1

Re: [Twisted-web] pgasync (was: /freeform_post!!random causes exceptions)
by J Turner Jan. 20, 2005

Jan. 20, 2005

On Tue, Jan 18, 2005 at 02:24:09PM +0100, Andrea Arcangeli wrote: > > I'm not a huge fan of *encouraging* the use of adbapi in new projects, > > however. DB API is used by every single other project. It's not really > > me that invented a new API. :) > > ;) The point is that I hava to depend on the twisted API for my app, not > on DB API. There is no way I can handle an unstable API for the DB side > while developing my app, the overhead would be too huge, I don't have > time to maintain two APIs and adbapi is the only one I'm confortable to > depend right now. I choosed python only to go in production as fast as I > possibly can, I've truly no time to help on what's not strictly need for > my app, not more than answering these emails ;). DB API is the API used by all the synchronous modules, which probably represent 99.9% of the python database code out there. There are two schools of thought on this one: 1.) Do it adbapi style to play well with legacy Twisted code, the twisted way 2.) Keep a very DB API-like setup to try to merge Twisted db development back toward the standard used by the rest of the python community (but with callbacks and release()). runQuery and runOperation are nice, and calls like those should be added in some clean way to pgasync, IMO. However, please, please use a cursor and do it the db api way if you're doing more than one execute(), and you want any kind of real transactional capability. adbapi doesn't really facilitate transactions all that well, unless you retrieve a cursor in runInteraction, and hey--cursors! Here we are back at DB API anyway. (Also the problems with runInteraction, that I explain below.) I'm just not sure how fully to embrace adbapi, and how to resolve the "right" API for pgasync. But I need to figure it out soon, because the protocol layer has been pretty stable for awhile now, and I'm already using pgasync in some production code on my end. I'd like to stop all this API shuffling ASAP. > > Plus, I cannot make a true runInteraction, since the called function is > > assumed to be executed in a thread. As far as runQuery() goes, that's > > basically connection.exFetch(). And runOperation is a trivial > > addition... > > What's the difference between running it in a thread or not? runInteraction takes a function as an argument. Traditionally, this function was always run in a thread, so you could be free to, for example, make a blocking call using urllib.urlopen or something. While pgasync could call the function that runInteraction passes to it, that function could *not* block. pgasync doesn't make a thread pool, and it won't (ever) run anything on a thread. That was the principal goal when I started the project: Twisted is async, so I want it all async. - jamwt

3 4