|
Rick Beton writes > In terms of Canterbury's relevancy in novel areas, I would like to mention two recent technologies that illustrate current diversity. Node-JS is a framework for _javascript_ execution (a 'JVM' for _javascript_) that is notionally single-threaded
and highly asynchronous. It might be seen as the antithesis of the event-driven process oriented approach: concurrency is entirely handled by callbacks and it requires callbacks within callbacks, nested to any number of levels in a way that can become quite
disorienting. In [1] it looks to me like Node.js has a rather reflected view on synchronous and asynchronous handling. Could you please elaborate, because I need to understand.
I assume itâs got to do with the callback programming paradigm (only)? [1] -
http://nodejs.org/api/all.html#all_process (Mr) Ãyvind Teig Senior development engineer, M.Sc. Autronica Fire and Security AS UTC CCS EMEA Fire & Security Operations Tel: +47 7358 2468
oyvind.teig@xxxxxxxxxxxxxxxx http://www.autronicafire.no/ http://www.teigfam.net/oyvind/work/work.html Fra: Sympa,pkg125 [mailto:sympa@xxxxxxxxxx]
PÃ vegne av Rick Beton Hi Peter, I feel that the work at Canterbury has been very necessary, quite distinctive, and a considerable but subtle benefit to the commercial business software in which I spend my time. One notable benefit has been from the educational materials in process oriented design with Java, such as Peter Welch's talks and presentation materials. This stream of insight has been quite distinctive in a software world where everyone
else is talking about asynchronous programming (which is unscalable and therefore ultimately much harder). Much business software is event driven, involving message passing queues etc. Clear ways of thinking through the issues are needed and the Canterbury
team have made a very worthwhile contribution here. We have been able to use JCSP in some very effective ways in a range of projects. The largest design-in was in the London Congestion Charge control centre. Here, JCSP orchestrates the Java server that collected the feeds from nearly 1000
cameras, with 7 tcp connections per camera. This task is highly concurrent and high volume (typically 1.5M records captured per day). Some of my projects have been of the 'one thread per request' Tomcat model. Such projects tend not to use any other explicit threads. But as soon as the design needs to vary the lifecycle from one thread per request to interacting with
longer-running threads, JCSP has been found to be an effective way of synchronising and exchanging data. In my work, JCSP is now also being used from Scala and other JVM-based languages. In terms of Canterbury's relevancy in novel areas, I would like to mention two recent technologies that illustrate current diversity. Node-JS is a framework for _javascript_ execution (a 'JVM' for _javascript_) that is notionally single-threaded
and highly asynchronous. It might be seen as the antithesis of the event-driven process oriented approach: concurrency is entirely handled by callbacks and it requires callbacks within callbacks, nested to any number of levels in a way that can become quite
disorienting. The other technology is the new Go language, which embodies CSP and a process oriented approach via its runtime scheduler that is similar (not surprisingly) to that in Occam. NodeJS and Go both date from around 2009 and highlight a world that
is emerging from a 15-year domination by Java. This shows us the importance of continuing the work at Canterbury - we already have a world-class centre for understanding concurrency in the process oriented model at a time that the world needs more of this
understanding. The Canterbury team have much to offer in terms of current and future technologies. I'd like to conclude with a few observations about Occam and the Kroc toolset. This has clearly been a potent tool for education and concurrency research. However, there is just a hint that we might have done more here. Compared to other
small language bases (perhaps Go for example), there have been some hurdles to wider adoption that could in principle have been overcome with a modest effort - the incomplete tool chain and the need for creating more modular code are the two issues I would
mention. I think that there needs to be more effort expended here - there is the potential for this work to have an active community of users, particularly in embedded logic and control systems, but it needs a small seed-corn to get it to a place where this
can flourish. Occam is the bed-rock of the highly-successful JCSP and deserves to do better. I see Occam and Go as siblings that occupy a similar minset but slightly different spaces and there will be clear benefits from keeping Occam in a usable state therefore.
There is potential for a healthy cross-fertilisation of ideas in their respective communities going into the future. In summary, there has been much work that has been of considerable benefit from the Canterbury team and I strongly recommend that this continues. I have a few ideas for taking this further - perhaps in addition there might be more investment
in Kroc as a vehicle for practical concurrency and for education, and more investment in cohesive literature such as a book on the process oriented approach on a variety of platforms. Kind regards, Rick Beton -- Big Bee Consultants Ltd On 24 May 2013 14:36, P.H.Welch <P.H.Welch@xxxxxxxxxx> wrote:
|