I've hit a problem as my app has got bigger (about 30-40 widgets now,
all chattering roughly once every 2 seconds) where the reliable
message delivery mechanism is spiralling out of control. It seems that
the constant back and forth means that large 'baskets' of messages are
resent. The more this happens, the busier everything gets until the
browser becomes unresponsive.
There's a fix for it: [Divmod-dev] athena duplicate messages issue but
I'm slightly concerned about the potential for lost messages - and
also confused about how this could happen. Given that HTTP is a
reliable connection-oriented transport, where is the gap that messages
can fall through?
I think I can cope with lost messages in most cases, so would it be
useful to add a kind of 'sendRemote' that was like 'callRemote' but
didn't care about a response? Or maybe this already exists and I've
P.S. this app is likely to get more noisy - is it likely that I'll
have to abandon Athena for Orbited or similar? I mean, are there
architectural differences that will prevent Athena scaling?
I am using Nevow's LiveElements and I am gettings troubles with the
docFactory attribute. In the examples I've seen, docFactory =
I'd like to load a string representing my html page
Can this be done? I really don't like stan :)
 I generate the string using Django's templates systems' render_to_string
I have the following setup (see below), in which the render method of
a RasterServer instance is responsible for generating a png file data
in memory that then should be passed on to the client that made the
However, I can't get my head around how to define the content-type for
the render method result? Or whether that's possible at all? If not,
how should I define my RasterServer so that it would return image/png
content to the client?
from twisted.web import resource, static, server
from twisted.application import service, strports
root = resource.Resource()
raster = RasterServer()
application = service.Application('test')
mo_server = strports.service(where, server.Site(root))
def render(self, request):
This example over-rides render (which I could probably do, but it seems like cheating):
This example is over my head (my zope.interfaces foo is weak):
and also possibly dated? twisted.web2.auth.wrapper.HTTPAuthResouce vs. twisted.web._auth.wrapper.HTTPAuthSessionWrapper
Is anyone aware of any other examples I could consider?
Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace.
Any dissemination, distribution or copying of the enclosed material is prohibited.
If you receive this transmission in error, please notify us immediately by e-mail
at abuse(a)rackspace.com, and delete the original message.
Your cooperation is appreciated.