| 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

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; Would This Have Been OK?; Honesty only important economically before institutions develop; Stegangraphy via PS4; OpenCL Mess; More Book Recommendations; Good Explanation of Difference Between Majority + Minority; Musical Chairs - Who's The Privileged White Guy; I can see straight men watching this conversation and laffing; Meta Thread Defending POC Causes POC To Close Account; Indigenous People Of Chile; Curry Recipe; Interesting Link On Marginality; A Nuclear Launch Ordered, 1962; More Book Recs (Better Person); It's Nuanced, And I Tried, So Back Off; Marx; The Negative Of Positive; Jenny Holzer Rocks

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

Tiny Workflow Language

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

Date: Wed, 8 Mar 2006 08:54:18 -0300 (CLST)

I think I may finally have understood this "business process" thing at
work today.  If the following still makes sense in the cold light of
tomorrow morning then I will implement it at work.

tiny.package-info: "A tiny workflow"
tiny.Annotated: class annotation:DomXml payload:Object
tiny.Test: interface DomXml->boolean
tiny.Sink: interface Annotated->void
tiny.Flow: interface extends Test, Sink
tiny.Process: class Filter Flow Object->void
tiny.sink.package-info: "Simple sinks for error handling"
tiny.sink.Throw: class<Sink Class<Exception>
tiny.sink.Silent: class<Sink
tiny.sink.LogMsg: class<Sink String (or XPath?)
tiny.sink.Log: class<Sink String (or XPath?)
tiny.test.package-info: "Tests using XML annotation"
tiny.test.Always: class<Test
tiny.test.Never: class<Test
tiny.test.XPath: class<Test XPathExpression
tiny.flow.package-info: "Build Flow-based sequences"
tiny.flow.All: class<Flow Test List<Flow>
tiny.flow.First: class<Flow Test List<Flow> Sink
tiny.flow.Pair: class<Flow Test Sink
tiny.input.package-info: "Conversion to the internal format"
tiny.input.Normalize: interface Object->boolean Object->Annotated
tiny.input.Filter: class List<Normalize> Sink
tiny.input.Name: class<Normalize String

Notes
- the Sinks in First and Filter are exception handlers
- assembly via constructors or setters (Spring)
- All + First give basic logic, sequencing, etc
- Support for single elements/arrays as well as lists, for easy config

The basic idea is that you define a Process that accepts an Object and
calls an appropriate Sink.  The input Object is processed by a matching
Filter to give an Annotated which combines the original Object with an Xml
annotation.  Subsequent processing decisions are based on the annotation,
which is passed to various Tests.

Realising that Flow was the only necessary component for constructing more
complex logic (ie that Test could be Always if the test were irrelevant)
was critical in simplifying the types.  Without that, classes in the flow
package had to manage various combinations of Test and Sink.

I think the set of operations above is sufficient for quite a range of
tasks.  It'll be interesting to see if (1) this is anything like the right
idea and (2) if so, how it compares to something like BEPL.

The most obvious things that are missing at the moment are:
- the ability to modify the annotation (state)
- sophisticated error handling

An example in Java might be:

  new Process(
    new Filter(
      new IngestRequestNormalize(),
      new Throw("Cannot normalize")),
    new First(
      new Flow[] {
        new TestSinkPair(
          new XPath("a/b/c/Mosaic"),
          new MosaicIngest())
        new TestSinkPair(
          new XPath("p/q/r/Echelle"),
          new EchelleIngest())},
      new Throw("Cannot ingest")))

That's a process that converts incoming data if it's an IngestRequest.
Converted data are then tested to see if they are from a Mosaic and, if
so, ingested.  If not, a test is made for Echelle data.  If that fails
too, an exception is raised.

In Spring it would be similar, but with properties.  I think it will look
pretty good.

Now I need to sleep.  Want to run tomorrow before work.

Andrew

Comment on this post