background preloader


Facebook Twitter

Signal vs. Noise by Basecamp — Business, Design, Programming and the Web. John Paul Morrison. John Paul Rodker Morrison (born John Paul Rodker in 1937) is a British-born Canadian computer programmer, and the inventor of flow-based programming (FBP).

John Paul Morrison

He is the author of the book Flow-Based Programming: A New Approach to Application Development, now in its 2nd edition .[1] He joined IBM UK in January 1959, as an EDPM (Electronic Data Processing Machines) Representative. Five years later, he moved to the US, and then to Montréal, Québec, Canada. While in Montréal, he started developing the ideas which led eventually to flow-based programming, whose concepts are now (roughly 40 years later) being picked up by major companies and computing practitioners world-wide.[4][5][6] He retired from IBM Canada in 1992, and still works as a contractor and consultant, promoting the concepts of FBP, and currently lives in historic Unionville, Ontario. References[edit] Jump up ^ J.

External links[edit] Biography of John Paul Morrison. Wiki: DrawFBP. DrawFBP The examples lower down on this page were drawn using the old DrawFBP program, written in C++.

Wiki: DrawFBP

However, a new Java version (DrawFBP-2.8.8) - - is now available - see FBPNews. For more complete information, see . DrawFBP is now running successfully under Java Web Start (JWS)! For those interested in trying it out, click on . Here is a sample network under construction: To give credit where credit is due, a number of usability ideas for the new tool are due to Oliver Brupbacher, of NumCom? There was a strange problem (Summer, 2013), where the Yes/No? Who produces DrawFBP? Yes, it's free - in fact, I would like people to enhance it. DrawFBP is a diagramming tool that allows the user to enter an FBP network graphically. Flow Based Programming - Google Groups. Flow-based programming. FBP is a particular form of dataflow programming based on bounded buffers, information packets with defined lifetimes, named ports, and separate definition of connections.[1] Introduction[edit] Because FBP processes can continue executing as long they have data to work on and somewhere to put their output, FBP applications generally run in less elapsed time than conventional programs, and make optimal use of all the processors on a machine, with no special programming required to achieve this.

Flow-based programming

The network definition is usually diagrammatic, and is converted into a connection list in some lower-level language or notation. FBP is thus a visual programming language at this level. More complex network definitions have a hierarchical structure, being built up from subnets with "sticky" connections. FBP promotes high-level, functional style of specifications that simplify reasoning about system behavior. History[edit] FBP was invented by J. Dataflow programming. In computer programming, dataflow programming is a programming paradigm that models a program as a directed graph of the data flowing between operations, thus implementing dataflow principles and architecture.

Dataflow programming

Dataflow programming languages share some features of functional languages, and were generally developed in order to bring some functional concepts to a language more suitable for numeric processing. Some authors use the term Datastream instead of Dataflow to avoid confusion with Dataflow Computing or Dataflow architecture, based on an indeterministic machine paradigm. Dataflow programming was pioneered by Jack Dennis and his graduate students at MIT in the 1960s. Dataflow architecture. Dataflow architecture is a computer architecture that directly contrasts the traditional von Neumann architecture or control flow architecture.

Dataflow architecture

Dataflow architectures do not have a program counter, or (at least conceptually) the executability and execution of instructions is solely determined based on the availability of input arguments to the instructions, so that the order of instruction execution is unpredictable: i. e. behavior is indeterministic. Although no commercially successful general-purpose computer hardware has used a dataflow architecture, it has been successfully implemented in specialized hardware such as in digital signal processing, network routing, graphics processing, telemetry, and more recently in data warehousing. It is also very relevant in many software architectures today including database engine designs and parallel computing frameworks.

History[edit] The research, however, never overcame the problems related to: How An Arcane Coding Method From 1970s Banking Software Could Save The Sanity Of Web Developers Everywhere. Today’s web programmers grapple with problems that people in the early days never had to deal with.

How An Arcane Coding Method From 1970s Banking Software Could Save The Sanity Of Web Developers Everywhere

They’re building complex UIs, juggling a bunch of APIs, and running multiple processes at the same time. All of these tasks require mastering the flow of data between application components in real-time, something which even the most advanced developers struggle with. Why can’t things be easier?


Thinking about the flow-based programming user interface - Henri Bergius in Berlin, Germany. As readers of this blog already know, I've been working on the NoFlo flow-based programming environment for JavaScript.

Thinking about the flow-based programming user interface - Henri Bergius in Berlin, Germany

Lately the development effort has received a large boost from both the EU-funded SmarcoS Project and client work, and so the question of a flow design UI has become even more urgent. In nutshell, flow-based programming (FBP) is a paradigm where programs are built from components that have a set of defined input and output ports.

These ports are then wired together to make a graph that defines the logic and the data flow. Where we are now At the moment there are two user interfaces that can be used for defining NoFlo graphs visually. This is the most functionally-complete FBP user interface, but is somewhat limited by Java's cross-desktop capabilities and the inability to introspect the information available via NoFlo's component loading interface. Traffic flow (computer networking) A TCP/IP flow can be uniquely identified by the following parameters within a certain time period: Source and Destination IP addressSource and Destination PortLayer 4 Protocol (TCP/UDP/ICMP) All packets with the same source address/port and destination address/port within a time period are considered as one flow.

Traffic flow (computer networking)