| C. V. Lopes, D: A language framework for distributed programming, Ph.d. thesis, Northestern University, ftp://ftp.ccs.neu.edu/pub/people/lieber/theses/ lopes/dissertation.pdf (1997). |
....the surgery on the execution process. Modern AOP demands that the crosscutting mechanism be general purpose, allowing modifying any code with respect to the structure of that code, not just a particular semantics. This contrasts with some of the earlier special purpose aspect languages [20]. Thus, a system that allows the user to define, say, security code to be invoked in particular contexts is a framework, not an AOP language. 4. MODIFYING THE INTERPRETER The purpose of this exercise is to ask what does one have to do to make AGPL aspect oriented Here we are concerned with ....
C. V. Lopes. D: A Language Framework for Distributed Programming. PhD thesis, College of Computer Science, Northeastern University, 1997.
....weaver. An aspect language designed to express a specific kind of aspect is highly desirable because it results in more concise and more intentional aspect declarations, making it easier to write aspects. A testament to this is the fact that many of the first aspect languages were aspect specific [11, 6, 10] and not general purpose. On the other hand, aspect specific languages are very powerful within their specific scope but they can only be applied to the specific aspect they were designed for. Because of this, many AOP related techniques [7, 15, 1] o#er a general purpose aspect language which ....
C. V. Lopes and G. Kiczales. D: A Language Framework for Distributed Programming. PhD thesis, College of Computer Science, Northeastern University, 1997.
....of trace information and modify the system accordingly. With different ########### ##### variants a language runtime can be built. 3. 1 Using Program Generation to Weave Aspects Currently the most common way to implement aspects are generative environments, such as AspectJ [10] HyperJ [20] D [13], ComposeJ [23] a tool for adding composition filters [2] to Java) or JAC [18] These follow a similar sequence. For illustration, we will give some examples from AspectJ. The other named generative environments use different terms and apply different transformations, but yet the basic ....
C. V. Lopes. D: A Language Framework for Distributed Programming. PhD thesis, College of Computer Science, Northeastern University, Dec 1997.
....e.g. encryption decryption, compression decompression, state saving and fault tolerance. We are also able to express through connectors coordination requirements (synchronization and concurrency) similar to those expressed using the aspect oriented language for coordination proposed in [15]; an example is presented in next section. The programmer can also write new connectors in Java to encapsulate any aspect or concern associated with module interaction. These connectors have the same treatment as normal modules and are specified using the ADL constructs. R RIO includes a ....
....implementation, i.e. separated managers can be used to take care of different parts of a running architecture. 3 An Example In this section we outline through an example some points of our proposal; we use a buffer application that is also presented in other related works, e.g. 3] [15]. For clarity, we avoided using abbreviated syntax constructs, configuration parameters, and ignore the error handling issue. CBabel, R RIO s ADL is described in [19] and [26] 3.1 Basic Architecture The graphical and textual representations of this producer consumer buffer architecture are ....
[Article contains additional citation context not shown here]
Lopes, C.I.V.; D: A Language Framework for Distributed Programming, Ph.D. Thesis, College of Computer Science, Northeastern University, Boston, USA 1997.
....to mediate real time requirements of a set of modules. In our project, as exempli ed in this section, we were able to express through connectors coordination (synchronization and concurrency) requirements similar to those expressed using the aspect oriented language for coordination proposed in [20]. We also managed to encapsulate into connectors the machinery required to support fault tolerance through server replication (see section 5.1) and found that diverse general purpose module interaction patterns can be mapped to connectors. In this section we also outline additional points of our ....
....5.1) and found that diverse general purpose module interaction patterns can be mapped to connectors. In this section we also outline additional points of our proposal. Initially, we customize a simple producer consumer bu er application, that is also presented in other related works, e.g. 3] [20]. Finally, we show how the contextualre ection capability of our connectors can be used for improving reuse. For clarity, in the examples, we avoided using con guration parameters, and ignore the error handling issue. CBabel, R RIO s ADL, is described in [24] and [32] module BufferApplication ....
[Article contains additional citation context not shown here]
Lopes, C.I.V.; D: A Language Framework for Distributed Programming, Ph.D. Thesis, College of Computer Science, Northeastern University, Boston, USA 1997.
....are called aspects and can be found in a software system s design as well as its implementation. As of today there are several approaches that support aspect oriented concepts, ranging from general purpose aspect languages like AspectJ [1, 13] to domainspecific aspect languages such as RG or D [15, 14]. Aspects extends the Squeak Smalltalk 2 environment to allow for experimental aspect oriented system development [8] It mainly draws on the results of two projects: the first is AspectJ from Xerox PARC, a general purpose aspect oriented language extension to Java, and the second is John Brant s ....
Lopes, C. V.: D: A Language Framework for Distributed Programming. Dissertation. College of Computer Science, Northeastern University, Boston, 1997
.... separate from the target distributed application is essentially a form of aspect oriented programming (AOP) 42] Similar language extensions have been previously proposed for specifying synchronization and or communication behavior of a class separately from the other methods of that class [43,44]. These language extensions served as models for this part of PCL. Finally, there has been extensive work on runtime platforms for supporting adaptive Grid applications at the level of middleware, runtime libraries, and network layer support. We can only cite a limited sample here. Globus [9] and ....
C. Lopes, D: A Language Framework for Distributed Programming, Ph.D. thesis, Northeastern Univ. (Nov. 1997).
....been defined in order to provide support for the representation of replicated objects. Moreover, a new language that helps programmers to build fault tolerance systems has been defined in [Fab97, Fab00] This proposal is based on the concept of separation of concerns and extends AspecJ language [Lop97] with replication primitives. It is possible to define the attributes that need replication and what to do when a replication error happens. But there is no way to express new replication actions or when replication must be executed. Although these models help programmers to implement fault ....
C.V. Lopes. D: A Language Framework for Distributed Programming. Phd Thesis 1997. University of Northeastern
....workflow resource model mentioned above is the synchronisation of the concurrent access of multiple activities to a single resource. Since synchronisation of concurrent threads was the first application of AOP and the main purpose for the specification of the domain specific aspect language COOL [9], the suitability of aspects in this area doesn t needs no further elucidation. 3.3 Auditing Perspective Monitoring and logging of workflow executions as well as a comprehensive evaluation of recorded audit trails is an essential part of workflow management, since it closes the workflow ....
Lopes, C.: D: A Language Framework for Distributed Programming. A Ph.D. Thesis. College of Computer Science. November 1997.
.... constraints for a class to be specified separately from the methods of that class [12] Lopes de scribes two languages, COOL and RIDL, that respectively allow synchronization constraints and communication behavior for a class to be specified separately from the methods of that class [19]. In each case, the language extensions are fairly small and are compiled down to the language of the base distributed application. In both cases, the synchronization and communication objects can inspect the state of the target object, but cannot modify that state. This is suf ficient for their ....
....because both authors assume that all communication happens via (remote or local) object invo cations and synchronization happens at method granularity. Lopes has shown that her approach leads to substantially simpler, more manageable programs, despite using just a few simple language extensions [19]. 3. TARGET APPLICATIONS This section describes two adaptive applications (a parallel scientific code and a distributed multimedia code) that have served as initial drivers for our research. Table i sum marizes the adaptation behavior of these codes, including the events that cause adaptation, ....
[Article contains additional citation context not shown here]
C. Lopes. D: A Language Framework for Distributed Programming. PhD thesis, Northeastern Univ., Nov. 1997.
....approach bytecode rewriting is not used since we have full access to the component compiler and instead of class loading interception the method calls are intercepted. 1 do not confuse this general purpose language with aspect language COOL developed by C. Lopes as a part of her Ph.D. thesis [5] 3 COOL and AspectCOOL In this section the component language COOL (Classroom Object Oriented Language) and the aspect language AspectCOOL are presented. The most important goal in the development of the AspectCOOL language was to explore the possibilities for separate compilation of components ....
C. V. Lopes. D: A Language Framework for Distributed Programming, Ph.D. Thesis. Graduate School of the College of Computer Science, Northeastern University, Boston, Massachusetts, 1997.
....modified, but its weaving behavior can be indirectly instructed by several predefined keywords. In such an approach, it assumes that by careful analysis of the intended computing aspect, a well predefined weaver can be enough to compose the functional component and the intended aspect component [10]. However, due to the closure of the domain specific weaver to adopt new weaving functions, programmers are therefore again forced to interleave aspect code in relation to other domains into functional components. On the contrary the general purposed aspect weaver can be considered as open and ....
....each other is prohibited. ## On the contrary, with the domain specific weaver, its mechanism for supporting aspect weaving of the intended computing domain is hidden from programmers and is not enclosed in the weaving components. For a domain specific language example in Figure 2, the language D [10] allows programmers to associate the functional component (e.g. buffer) with the weaving component (e.g. bufferCoord) and the mechanism for the coordination of threads is not implemented by programmers but taken cared by the hidden aspect weaver. In this way, the domain specific weaver ....
Lopes, C.V., Kiczales G., D: A Language Framework for Distributed Programming, Xerox PARC, Palo Alto, CA. Technical report SPL97-010 P9710047, February 1997.
.... removeBook( roomNumber shelfNumber Fig. 6: Base Library Design Example 1: Synchronisation Aspect This first cross cutting requirement is that the book manager should handle several requests to manage books and their locations concurrently. This aspect example, first described in [12], supports the book manager handling several read requests concurrently, while temporarily blocking write requests. Individual write requests should block all other services. Pattern Specification Synchronisation of concurrent processes is a common requirement, and therefore it is useful ....
C. Lopes and G. Kiczales. D: A Language Framework for Distributed Programming. Technical report SPL97010. Xerox PARC, 1997. http://www.parc. xerox.com/csl/projects/aop/.
No context found.
Lopes, C.V. and G. Kiczales, D: A Language Framework for Distributed Programming, in Submitted for Possible Publication, OOPSLA 97. 1997.
No context found.
C. V. Lopes, D: A language framework for distributed programming, Ph.d. thesis, Northestern University, ftp://ftp.ccs.neu.edu/pub/people/lieber/theses/ lopes/dissertation.pdf (1997).
No context found.
C. Lopes. D: A Language Framework for Distributed Programming. PhD thesis, College of Computer Science, Northeastern University, November 1997.
No context found.
C. Lopes, A language framework for distributed programming, PhD thesis, Northeastern university, 1997
No context found.
C. V. Lopes. D: A Language Framework for Distributed Programming. PhD thesis, College of Computer Science, Northeastern University, 1997.
No context found.
C. V. Lopes. D: A Language Framework for Distributed Programming. PhD thesis, College of Computer Science, Northeastern University, Dec 1997.
No context found.
C. Lopes. D: A Language Framework for Distributed Programming. PhD thesis, College of Computer Science, Northeastern University, Dec. 1997.
No context found.
Lopes, C. V.: D: A Language Framework for Distributed Programming. Dissertation. College of Computer Science, Northeastern University, Boston, 1997.
No context found.
C. V. Lopes. D: A Language Framework for Distributed Programming. PhD thesis, College of Computer Science, Northeastern University, Dec 1997.
No context found.
C. Lopes and C. Kiczales. D: A language framework for distributed programming. In Technical Report SPL97-010, P9710047, Xerox Palo Alto Research Center, 1997.
No context found.
C. V. Lopes and G. Kiczales, D: A Language Framework for Distributed Programming, Technical Report SPL97-010, Xerox Palo Alto Research Center (February 1997).
No context found.
C. Lopes, A language framework for distributed programming, PhD thesis, Northeastern university, 1997
First 50 documents Next 50
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