Mailman 3 March 2012 - Twisted-web

Test
by Philippe Lafoucrière 05 Aug '21

05 Aug '21

Hi all just a test

3 2

accessing tls session from twisted web
by Ilja Livenson 20 Mar '12

20 Mar '12

Hi, all I have a twisted web server, exposing https interface. What I'm trying to do now is to support usage of two-way tls authentication and use data from the client certificate as a seed for authenticated avatar. Any hints as to how to do that in the best way? I guess it should be done before Realm's requestAvatar method is called? thanks for your input! Ilya PS. Roughly speaking the code for that part looks like this: wrapper = guard.HTTPAuthSessionWrapper(Portal(SimpleRealm(), used_checkers), authn_methods) reactor.listenSSL(8080, server.Site(resource=wrapper), contextFactory = sslContext)

1 0

CorePost 0.0.14 is out: automatic parsing of arguments from JSON, YAML and XML docs
by Jacek Furmankiewicz 19 Mar '12

19 Mar '12

Version 0.0.14 of the CorePost Twisted REST microframework is out. This new release has a nice set of enhancements for automatically parsing incoming JSON, YAML or XML document payloads and extracting them for arguments into router methods: Documented on github: http://jacek99.github.com/corepost/argument_parsing.html Cheers Jacek

1 0

PB vs Foolscap vs AMP?
by Jacek Furmankiewicz 10 Mar '12

10 Mar '12

Hi, I am trying to do some research on what is the most performant method for a Twisted server to speak to a client running in a separate process. The default solution in Twisted seems to be Perspective Broker, but then there is AMP and Foolscap as well. Has anyone ever done any benchmarks comparing those? I'd like to have an idea as to which one is most likely to give me the best performance. Thanks in advance Jacek

3 3

CorePost 0.0.12 is out
by Jacek Furmankiewicz 08 Mar '12

08 Mar '12

Support for more advanced, nested URL routing with dynamic paths, for building more complex REST apps with multiple nested services: http://pypi.python.org/pypi/CorePost/ Due to some architectural changes, it contains some backwards incompatible changes (minor). Migration steps documented in release notes. Jacek

1 1

Get access to Avatar from Resource object?
by Jacek Furmankiewicz 05 Mar '12

05 Mar '12

I am trying to understand how Twisted Web security works, based on a few links: http://jcalderone.livejournal.com/53074.html http://twistedmatrix.com/documents/current/web/howto/web-in-60/http-auth.ht… They all explain how to set up a web app with let's say HTTP auth. But there are no examples on how a Resource method (let;s say render_GET) could get access to the current Avatar object? And does the Avatar object need to implement some specific interface? What I want to do in CorePost is to allow fine grained privilege-based security *per method* (similar in style to Spring Security, for those who know it), e.g.: @route("/user",Http.GET) @secured("BROWSE_USER") def getUser(self,request,**kwargs): return ...some user info... @route("/user",Http.POST) @secured("UPDATE_USER") def updateUser(self,request,userId,**kwargs): ...create new user, etc... If the Avatar does not have the required privileges (e.g. "BROWSE_USER" or "UPDATE_USER" in the example above), I want to throw a 403 Access Denied automatically. Thanks for any pointers Jacek https://github.com/jacek99/corepost

7 18

Leaf Resources with child Leaf Resources
by Jacek Furmankiewicz 03 Mar '12

03 Mar '12

>From what I understand, once a Resource isLeaf = True, it cannot have child Resources of its own (no requests seem to get routed to them). This is not really a realistic scenario in a typical REST application where nested REST services are common, e.g. Customer REST service: *GET /services/customer* *POST /services/customer* *PUT /services/customer/<customerId>* *DELETE /services/customer/<customerId>* Customer Address REST service: *GET /services/customer/<customerId>/address* *POST /services/customer/<customerId>/address* *PUT /services/customer/<customerId>/address/<addressId>* *DELETE /services/customer/<customerId>/address/<addressId>* and so on and so forth.... The only way I can support this in CorePost is to separate the concept of a Twisted.Web Resource from a standalone REST service for a particular entity. So let's say I would have a root CorePost Resource hooked up to 'services' and it would have a child collection of REST service classes and manage routing the requests to the appropriate one. Each of the REST services for an entity underneath that core Resource would NOT be a twisted.web Resource but just a regular class. Does this sound correct? Or am I missing some way of using twisted.web Resource objects that would allow me to accomplish the same thing without moving away from Resource as the ancestor of all my REST service classes? Thanks Jacek

3 12