Andrew Cooke | Contents | Latest | RSS | 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

Choochoo Training Diary

Last 100 entries

[Programming] React Leaflet; AliExpress Independent Sellers; Applebaum - Twilight of Democracy; [Politics] Back + US Elections; [Programming,Exercise] Simple Timer Script; [News] 2019: The year revolt went global; [Politics] The world's most-surveilled cities; [Bike] Hope Freehub; [Restaurant] Mama Chau's (Chinese, Providencia); [Politics] Brexit Podcast; [Diary] Pneumonia; [Politics] Britain's Reichstag Fire moment; install cairo; [Programming] GCC Sanitizer Flags; [GPU, Programming] Per-Thread Program Counters; My Bike Accident - Looking Back One Year; [Python] Geographic heights are incredibly easy!; [Cooking] Cookie Recipe; Efficient, Simple, Directed Maximisation of Noisy Function; And for argparse; Bash Completion in Python; [Computing] Configuring Github Jekyll Locally; [Maths, Link] The Napkin Project; You can Masquerade in Firewalld; [Bike] Servicing Budget (Spring) Forks; [Crypto] CIA Internet Comms Failure; [Python] Cute Rate Limiting API; [Causality] Judea Pearl Lecture; [Security, Computing] Chinese Hardware Hack Of Supermicro Boards; SQLAlchemy Joined Table Inheritance and Delete Cascade; [Translation] The Club; [Computing] Super Potato Bruh; [Computing] Extending Jupyter; Further HRM Details; [Computing, Bike] Activities in ch2; [Books, Link] Modern Japanese Lit; What ended up there; [Link, Book] Logic Book; Update - Garmin Express / Connect; Garmin Forerunner 35 v 230; [Link, Politics, Internet] Government Trolls; [Link, Politics] Why identity politics benefits the right more than the left; SSH Forwarding; A Specification For Repeating Events; A Fight for the Soul of Science; [Science, Book, Link] Lost In Math; OpenSuse Leap 15 Network Fixes; Update; [Book] Galileo's Middle Finger; [Bike] Chinese Carbon Rims; [Bike] Servicing Shimano XT Front Hub HB-M8010; [Bike] Aliexpress Cycling Tops; [Computing] Change to ssh handling of multiple identities?; [Bike] Endura Hummvee Lite II; [Computing] Marble Based Logic; [Link, Politics] Sanity Check For Nuclear Launch; [Link, Science] Entropy and Life; [Link, Bike] Cheap Cycling Jerseys; [Link, Music] Music To Steal 2017; [Link, Future] Simulated Brain Drives Robot; [Link, Computing] Learned Index Structures; Solo Air Equalization; Update: Higher Pressures; Psychology; [Bike] Exercise And Fuel; Continental Race King 2.2; Removing Lowers; Mnesiacs; [Maths, Link] Dividing By Zero; [Book, Review] Ray Monk - Ludwig Wittgenstein: The Duty Of Genius; [Link, Bike, Computing] Evolving Lacing Patterns; [Jam] Strawberry and Orange Jam; [Chile, Privacy] Biometric Check During Mail Delivery; [Link, Chile, Spanish] Article on the Chilean Drought; [Bike] Extended Gear Ratios, Shimano XT M8000 (24/36 Chainring); [Link, Politics, USA] The Future Of American Democracy; Mass Hysteria; [Review, Books, Links] Kazuo Ishiguro - Never Let Me Go; [Link, Books] David Mitchell's Favourite Japanese Fiction; [Link, Bike] Rear Suspension Geometry; [Link, Cycling, Art] Strava Artwork; [Link, Computing] Useful gcc flags; [Link] Voynich Manuscript Decoded; [Bike] Notes on Servicing Suspension Forks; [Links, Computing] Snap, Flatpack, Appimage; [Link, Computing] Oracle is leaving Java (to die); [Link, Politics] Cubans + Ultrasonics; [Book, Link] Laurent Binet; VirtualBox; [Book, Link] No One's Ways; [Link] The Biggest Problem For Cyclists Is Bad Driving; [Computing] Doxygen, Sphinx, Breathe; [Admin] Brokw Recent Permalinks; [Bike, Chile] Buying Bearings in Santiago; [Computing, Opensuse] Upgrading to 42.3; [Link, Physics] First Support for a Physics Theory of Life; [Link, Bike] Peruvian Frame Maker; [Link] Awesome Game Theory Tit-For-Tat Thing; [Food, Review] La Fabbrica - Good Italian Food In Santiago; [Link, Programming] MySQL UTF8 Broken; [Link, Books] Latin American Authors

© 2006-2017 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