| Andrew Cooke | Contents | Latest | RSS | Twitter | Previous | Next

C[omp]ute

Welcome to my blog, which was once a mailing list of the same name and is still generated by mail. Please reply via the "comment" links.

Always interested in offers/projects/new ideas. Eclectic experience in fields like: numerical computing; Python web; Java enterprise; functional languages; GPGPU; SQL databases; etc. Based in Santiago, Chile; telecommute worldwide. CV; email.

Personal Projects

Lepl parser for Python.

Colorless Green.

Photography around Santiago.

SVG experiment.

Professional Portfolio

Calibration of seismometers.

Data access via web services.

Cache rewrite.

Extending OpenSSH.

C-ORM: docs, API.

Last 100 entries

Have to add...; Culturally Liberal and Nothing More; Weird Finite / Infinite Result; Your diamond is a beaten up mess; Maths Books; Good Bike Route from Providencia / Las Condes to Panul\; Iain Pears (Author of Complex Plots); Plum Jam; Excellent; More Recently; For a moment I forgot StackOverflow sucked; A Few Weeks On...; Chilean Book Recommendations; How To Write Shared Libraries; Jenny Erpenbeck (Author); Dijkstra, Coins, Tables; Python libraries error on OpenSuse; Deserving Trump; And Smugness; McCloskey Economics Trilogy; cmocka - Mocks for C; Concept Creep (Americans); Futhark - OpenCL Language; Moved / Gone; Fan and USB issues; Burgers in Santiago; The Origin of Icosahedral Symmetry in Viruses; autoenum on PyPI; Jars Explains; Tomato Chutney v3; REST; US Elections and Gender: 24 Point Swing; PPPoE on OpenSuse Leap 42.1; SuperMicro X10SDV-TLN4F/F with Opensuse Leap 42.1; Big Data AI Could Be Very Bad Indeed....; Cornering; Postcapitalism (Paul Mason); Black Science Fiction; Git is not a CDN; Mining of Massive Data Sets; Rachel Kaadzi Ghansah; How great republics meet their end; Raspberry, Strawberry and Banana Jam; Interesting Dead Areas of Math; Later Taste; For Sale; Death By Bean; It's Good!; Tomato Chutney v2; Time ATAC MX 2 Pedals - First Impressions; Online Chilean Crafts; Intellectual Variety; Taste + Texture; Time Invariance and Gauge Symmetry; Jodorowsky; Tomato Chutney; Analysis of Support for Trump; Indian SF; TP-Link TL-WR841N DNS TCP Bug; TP-Link TL-WR841N as Wireless Bridge; Sending Email On Time; Maybe run a command; Sterile Neutrinos; Strawberry and Banana Jam; The Best Of All Possible Worlds; Kenzaburo Oe: The Changeling; Peach Jam; Taste Test; Strawberry and Raspberry Jam; flac to mp3 on OpenSuse 42.1; Also, Sebald; Kenzaburo Oe Interview; Otake (Kitani Minoru) move Black 121; Is free speech in British universities under threat?; I am actually good at computers; Was This Mansplaining?; WebFaction / LetsEncrypt / General Disappointment; Sensible Philosophy of Science; George Ellis; Misplaced Intuition and Online Communities; More Reading About Japan; Visibilty / Public Comments / Domestic Violence; Ferias de Santiago; More (Clearly Deliberate); Deleted Obit Post; And then a 50 yo male posts this...; We Have Both Kinds Of Contributors; Free Springer Books; Books on Religion; Books on Linguistics; Palestinan Electronica; Books In Anthropology; Taylor Expansions of Spacetime; Info on Juniper; Efficient Stream Processing; The Moral Character of Crypto; Hearing Aid Info; Small Success With Go!; Re: Quick message - This link is broken; Adding Reverb To The Echo Chamber; Sox Audio Tools

© 2006-2015 Andrew Cooke (site) / post authors (content).

Nested Handler Mappings in Spring

From: "andrew cooke" <andrew@...>

Date: Tue, 14 Mar 2006 19:20:02 -0400 (CLT)

The MVC support in Spring includes the idea of handler mappings - an
incoming HTTP request is passed to an (ordered) set of handlers, and each
in turn attempts to provide a controller.  This is nice, because
controllers are typically associated with URLs, so you can put the URL to
controller login in the handler (note to self - maybe I can do more of
that).

I have generic handlers that do things like pull parameters from the end
of URLs (a simple kind of URL rewriting), for example.  Others that make
decisions based on the state of the database (for URLs associated with
objects that have several significantly different states -
design/preparation and use, for example).

However, there are times when you really want to chain Handlers.  This
isn't possible with standard Spring because (1) the thing returned by a
handler should be a controller, not another handler and (2) every bean
that is an instance of the handler interface is pulled from the context
and called directly - you don't specify the handler list explicitly.

The second point means that there's a risk that your nested handlers are
called directly.

However, one useful wrinkle - handlers return Object.  So there's nothing
in the method signature to stop one handler returning another.

So, what to do?  I tried writing a different interface, but that didn't
work so well - sometimes it's not clear whether a handler should be a top
level handler or a nested level handler (if it's generic, it may be both).
 And a lot of functionality was provided by Spring superclasses, so
starting a new hierarchy lost much of that.

I couldn't find a perfect solution, but in the end I've gone with the
following, which works pretty well:

- an IterationHandler that drives the iterative process.  This is a top
level handler has a subhandler which it calls and, if that returns a
handler itself, it calls that handler in turn.

- the IterationHandler also propogates interceptors along the chain.  This
saves you from having to define the same bunch of interceptors for all
nested handlers - you just put them in the top IteratorHandler.

- a NestableHandler abstract class extends AbstractHandlerMapping and
checks the Session attributes to see if IterationHandler has set a flag. 
This indicates whether or not the subclass is being called at the top
level, and is compared against a configuration parameter.  If a handler is
intended only for nested use then it returns null when called directly -
this is the normal way for handlers to "pass".

- the NestedHandler implements AbstractHandlerMapping's getHandlerInternal
interface as final, passing checked calls to a second, abstract method. 
In this way any subclass automatically (and unavoidably) is checked.

So it works pretty much as required - the only nuisance is that extra
calls may be made from the top level to handlers that will not return
controllers.  I think this can be avoided by making the bean anonymous
(nesting its definition in the IterationHandler bean within Spring). 
However, that is not always desirable.

Andrew

Comment on this post