“ The Network as a Language Construct”, that came out of the work on Marketplace: This introduced a new ability that features prominently inĭataspace-based programming: the ability of a program to react toĭemand for some service or resource by producing supply of thatĪn example of this can be seen in the TCP echo server example given in an ESOP 2014 paper IĬo-wrote with Sam Tobin-Hochstadt and Matthias Felleisen, Level two would carry notifications describing the presence of Presence or absence of publishers and subscribers at level zero. The ideas in os2.rkt therefore evolved into a system calledĪt the lowest level, level zero, would be publishers andĪt level one would be presence notifications describing the Interested in any topic matching a wildcard, (contents-of _). Knowing about the existence of any subscribers that are in turn The solution is to have an “HTTP client driver” express interest in (Interest in (interest in (interest in (interest in … in messages)))) Matching publisher topic of that form: there are an unbounded number We can’t pre-create actors offering to publish on each possible It could subscribe to a topic (contents-of the-url ). Programs that would react to the presence of programs that would reactĮxample, consider a program that wants the contents of the document atĪ URL. Presence, but observation of observation of presence - that is, Some programs were naturally expressed using not mere observation of Programs like my DNS and SSH implementations. It turned out that the specialized form of state-replication andĬounterparty presence notification wasn’t enough to elegantly capture 2012–2014 Marketplace, Network Calculus, and Minimart All of the subsequent systems useĪctor behaviour types morally equivalent to that of os2.rkt, as “publishers” and “subscribers” that can see each others’ presence as Mechanism of dataspaces in the specialized form of “topics”, Here we can already see the seeds of the generalized state-replication Incorporating counterparty presence notifications alongside regular Actor-style message delivery. System” suitable for writing communicating and interactive programs.Ī small, pure-functional “operating system” for Racket called os2.rkt, based around an Would let me distill a general model of a “functional operating “big-bang” functional interactive graphics system, The idea was that the lessons from these, combined with my previousĮrlang and RabbitMQ experience, and ideas from Racket’s SSH client/server protocol implementation. Network-protocol-related services including a The first direction I followed was to use Racket to build a number of The Syndicated Actor model, Dataspaces, and the Syndicate DSL are the The communication primitives we choose for our programming languagesĪnd programming models could be drawn more directly from our Interprocess communication might be networking. Toward a PhD in programming languages with Matthias Felleisen.įor my PhD work, I explored the converse of Metcalfe’s idea: whether Inspired by this, by our work on RabbitMQ, and by my own observationsĪnd experiments, I left industry for a few years in academia, studying Networking is interprocess communication. Working on large-scale message broker federation,īook.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |