REST application model fragments from 1994
in a recent blog entry "EAI DSL", Gergor Hohpe mentions that back in
1994 he wrote a little domain specific language to aid screen
scraping based integration. Essentially the intention of the language
was to simplify reacting to changes in the scraped UI.
Here is a code fragment:
;---- scrape XYZ screen ----
FIND "INACT DT"
I find it interesting, that this looks a lot like what one would
write to resemble the browsing and drilling-down patterns of REST's
application model. Imagine an RDF enabled user agent - 'FIND
"ADDRESS"' (properly redone for RDF of course) could well mean: go do
a GET, traverse the hypermdia links until you find something that can
be inferred to be an address and "EXTRACT CITY" would then give us
the foo:city of that address.
Making use of this programatically would remove the need for a
document-type based coupling (e.g. this GET has to respond with an
address) between client and server and instead emphasize traversal of
hyperlinks until some stated information need is satisfied.
Back in 94...how smart!
- Hmm. This looks (at least to me) vaguely similar to Rails functional tests:def test_showget :show, :id => 1assert_response :successassert_template 'show'assert_not_nil assigns(:thing)assert assigns(:thing).valid?endI wonder if there's an underlying design model one could abstract into a generic DSL for this sort of thing...-- Ernie P.On Jun 8, 2006, at 6:33 AM, Jan Algermissen wrote: