S. Michiels, F. Matthijs, D. Walravens, and P. Verbaeten. DiPS: A Unifying Approach for Developing System Software. Position paper in in Operating Systems (HotOS-VIII), May 2001.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....of the stack should be as automatic as possible and the user shouldn t need to be bothered with the communication subsystem that should just work in any environment. The run time support for coping with dynamic protocol stack changes is assured by DiPS (Distrinet Protocol Stack) Mat99] [MMWV00]) our framework for building network subsystems. The DIPS framework provides the necessary support for the plumbing of layers and components, and run time support for the dynamic behavior. The DIPS framework is able to build stacks with different degrees of customizability. There are other ....

Sam Michiels, Frank Matthijs, Dirk Walravens, Pierre Verbaeten, DiPS: A Unifying Approach for Developing System Software, The 8th Workshop on Hot Topics in Operating Systems (HotOS-VIII). May 2001

No context found.

S. Michiels, F. Matthijs, D. Walravens, and P. Verbaeten. DiPS: A Unifying Approach for Developing System Software. Position paper in in Operating Systems (HotOS-VIII), May 2001.

....of the system needs to be adapted and how. This requires self monitoring. Seltzer [16] 17] presents similar ideas on self monitoring and selfadaptation. Concurrency and separation of concerns. A critical element in our concurrency research is the separation of concurrency from functional code [12], 10] Kiczales [8] de nes non functional concerns as aspects that cross cut functional code. An aspect (for example concurrency) is written in PR PF Unit PacketReceiver PacketForwarder Figure 1: A DiPS Component a speci c aspect language and is woven into the functional code by a so called ....

....hit Figure 2: A DiPS pipe for a simple le system tems or protocol stacks. The main goal of DiPS is to support reuse and adaptation at design time [11, 18, 19] as well as at run time [7] It therefore clearly separates di erent aspects such as interaction and concurrency from each other [12]. DiPS basics. A DiPS component can be seen as a building block (Unit) surrounded with an explicit entry and exit point (resp. PacketReceiver and PacketForwarder) Figure 1 shows a basic DiPS component. The Unit encapsulates the characteristics of a component. Data is sent through DiPS ....

S. Michiels, F. Matthijs, D. Walravens, and P. Verbaeten. DiPS: A Unifying Approach for Developing System Software. In A. D. Williams, editor, Proceedings - The Eigth Workshop on Hot Topics in Operating Systems, page 175. University of Karlsruhe, IEEE Computer Society, 2001.

....Section 4 describes how multi threaded software can be tested in DiPSUnit. Section 5 describes how units are tested in the presence of external control ows. Section 6 validates DiPSUnit in two case studies. Conclusions are formulated in section 7. 2 The DiPS framework We present DiPS [8] [10] as a Java component framework based on ne grained independent units that are connected as a pipe and lter architecture. The framework supports the development of system software such as protocol stacks or le systems [9] DiPS implementations of network protocols (such as TCP, UDP, IPv4, IPv6 ....

S. Michiels, F. Matthijs, D. Walravens, and P. Verbaeten, DiPS: A Unifying Approach for Developing System Software, Position paper in Proceedings of the 8th Workshop on Hot Topics in Operating Systems (HotOS-VIII), K.U.Leuven, Dept. of Computer Science, May 2001. 17

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC