| 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

Textbook for "QM as complex probabilities"; SFO Get Libor Trader (14 years); Why Are There Still So Many Jobs?; Navier Stokes Incomplete; More on Benford; FBI Claimed Vandalism; Architectural Tessellation; Also: Go, Blake's 7; Delusions of Gender (book); Crypto AG DID work with NSA / GCHQ; UNUMS (Universal Number Format); MOOCs (Massive Open Online Courses); Interesting Looking Game; Euler's Theorem for Polynomials; Weeks 3-6; Reddit Comment; Differential Cryptanalysis For Dummies; Japanese Graphic Design; Books To Be Re-Read; And Today I Learned Bugs Need Clear Examples; Factoring a 67 bit prime in your head; Islamic Geometric Art; Useful Julia Backtraces from Tasks; Nothing, however, is lost with less discomfort than that which, when lost, cannot be missed; Article on Didion; Cost of Living by City; British Slavery; Derrida on Metaphor; African SciFi; Traits in Julia; Alternative Japanese Lit; Pulic Key as Address (Snow); Why Information Grows; The Blindness Of The Chilean Elite; Some Victoriagate Links; This Is Why I Left StackOverflow; New TLS Implementation; Maths for Physicists; How I Am 8; 1000 Word Philosophy; Cyberpunk Reading List; Detailed Discussion of Message Dispatch in ParserCombinator Library for Julia; FizzBuzz in Julia w Dependent Types; kokko - Design Shop in Osaka; Summary of Greece, Currently; LLVM and GPUs; See Also; Schoolgirl Groyps (Maths); Japanese Lit; Another Example - Modular Arithmetic; Music from United; Python 2 and 3 compatible alternative.; Read Agatha Christie for the Plot; A Constructive Look at TempleOS; Music Thread w Many Recommendations; Fixed Version; A Useful Julia Macro To Define Equality And Hash; k3b cdrom access, OpenSuse 13.1; Week 2; From outside, the UK looks less than stellar; Huge Fonts in VirtualBox; Keen - Complex Emergencies; The Fallen of World War II; Some Spanish Fiction; Calling C From Fortran 95; Bjork DJ Set; Z3 Example With Python; Week 1; Useful Guide To Starting With IJulia; UK Election + Media; Review: Reinventing Organizations; Inline Assembly With Julia / LLVM; Against the definition of types; Dumb Crypto Paper; The Search For Quasi-Periodicity...; Is There An Alternative To Processing?; CARDIAC (CARDboard Illustrative Aid to Computation); The Bolivian Case Against Chile At The Hague; Clear, Cogent Economic Arguments For Immigration; A Program To Say If I Am Working; Decent Cards For Ill People; New Photo; Luksic And Barrick Gold; President Bachelet's Speech; Baltimore Primer; libxml2 Parsing Stream; configure.ac Recipe For Library Path; The Davalos Affair For Idiots; Not The Onion: Google Fireside Chat w Kissinger; Bicycle Wheels, Inertia, and Energy; Another Tax Fraud; Google's Borg; A Verion That Redirects To Local HTTP Server; Spanish Accents For Idiots; Aluminium Cans; Advice on Spray Painting; Female View of Online Chat From a Male; UX Reading List; S4 Subgroups - Geometric Interpretation; Fucking Email; The SQM Affair For Idiots

© 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