people
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
people [2008/06/26 01:50] – wdmeuter | people [2008/11/06 15:47] – alombide | ||
---|---|---|---|
Line 11: | Line 11: | ||
[[ http:// | [[ http:// | ||
- | In the past, I have been active in the design and formalisation of prototype-based object-oriented programming languages. After a small detour in AOP (where I introduced monads in AOP and identified the need for cflow with jumping aspects), I'm currently working with the ambient group on the design and implementation of ambient-oriented programming languages. My current mission is to come up with language constructs that makes writing software for loosely coupled (mobile) distributed systems as much fun as writing | + | In the past, I have been active in the design and formalisation of prototype-based object-oriented programming languages. After a small detour in AOP (where I introduced monads in AOP and identified the need for cflow with jumping aspects), I'm currently working with the ambient group on the design and implementation of ambient-oriented programming languages. My current mission is to come up with language constructs that make writing software for loosely coupled (mobile) distributed systems as much fun as writing sequential |
Keywords are repls, interpreters, | Keywords are repls, interpreters, | ||
Line 20: | Line 20: | ||
[[http:// | [[http:// | ||
- | My area of interest is memory management for distributed systems. More specifically, | + | My area of interest is memory management for distributed systems. More specifically, |
===== | ===== | ||
Line 26: | Line 26: | ||
[[http:// | [[http:// | ||
- | I am interested | + | The dynamic nature of ambient oriented applications makes it impossible to structure them as monolithic programs with a fixed input and output. Instead, a distributed event-driven architecture is required. Current event-driven architectures require distributed application components to react to events via a carefully crafted network of observers, event handlers or callback mechanisms which are scattered throughout the application code and can be triggered at any point in time. Such architectures are hard to develop, understand |
+ | |||
+ | This poses a problem when we look at the new generation of disposable processing hardware, such as RFID tags. Ubiquitous applications will not only consist of peer-to-peer interactions, | ||
+ | |||
+ | I am currently looking into programming abstractions that allow to specify which events to capture by distributed application components in a mobile | ||
===== | ===== |
people.txt · Last modified: 2018/04/12 22:07 by elisag