Розробка розподіленної системи розпізнавання автомобільних номерів

Метою даної роботи є розробка клієнт-серверної програмної системи для спрощення контролю за автотранспортом на автостоянках. Для розробки програмного забезпечення використана технологія .NET Remoting. Програмний продукт написано мовою C#.Целью данной работы является разработка клиент-серверной программной системы для упрощения контроля за автотранспортом на автостоянках. Для разработки программного обеспечения использована технология .NET Remoting. Программный продукт написан на языке C#.Purpose of this work is elaboration of client-server program system for control simplification after a motor transport on the car park. The .NET Remoting technology is used for software development. A software product is developed by C#

Розробка розподіленної системи розпізнавання автомобільних номерів

Мета роботи - розробка клієнт-серверної програмної системи для спрощення контролю за автотранспортом на автостоянках. Для розробки програмного забезпечення використано технологію .NET Remoting. Програмний продукт написано мовою C.Purpose of this work is elaboration of client-server program system for control simplification after a motor transport on the car park. The .NET Remoting technology is used for software development. A software product is developed by C#

A Comparative Evaluation of .net Remoting and JAVA RMI

Distributed application technologies such as Micrososoft.NET Remoting, and Java Remote Method Invocation (RMI) have evolved over many years to keep up with the constantly increasing requirements of the enterprise. In the broadest sense, a distributed application is one in which the application processing is divided among two or more machines. Distributed middleware technologies have made significant progress over the last decade. Although Remoting and RMI are the two of most popular contemporary middleware technologies, little literature exists that compares them. In this paper, we study the issues involved in designing a distributed system using Java RMI and Microsoft.NET Remoting. In order to perform the comparisons, we designed a distributed distance learning application in both technologies. In this paper, we show both similarities and differences between these two competing technologies. Remoting and RMI both have similar serialization process and let objects serialization to be customized according to the needs. They both provide support to be able to connect to interface definition language such as Common Object Request Broker Architecture (CORBA). They both contain distributed garbage collection support. Our research shows that programs coded using Remoting execute faster than programs coded using RMI. They both have strong support for security although implemented in different ways. In addition, RMI also has additional security mechanisms provided via security policy files. RMI requires a naming service to be able to locate the server address and connection port. This is a big advantage since the clients do not need to know the server location or port number, RMI registry locates it automatically. On the other hand, Remoting does not require a naming service; it requires that the port to connect must be pre-specified and all services must be well-known. RMI applications can be run on any operating system whereas Remoting targets Windows as the primary platform. We found it was easier to design the distance learning application in Remoting than in RMI. Remoting also provides greater flexibility in regard to configuration by providing support for external configuration files. In conclusion, we recommend that before deciding which application to choose careful considerations should be given to the type of application, platform, and resources available to program the application

RAFDA: A Policy-Aware Middleware Supporting the Flexible Separation of Application Logic from Distribution

Middleware technologies often limit the way in which object classes may be used in distributed applications due to the fixed distribution policies that they impose. These policies permeate applications developed using existing middleware systems and force an unnatural encoding of application level semantics. For example, the application programmer has no direct control over inter-address-space parameter passing semantics. Semantics are fixed by the distribution topology of the application, which is dictated early in the design cycle. This creates applications that are brittle with respect to changes in distribution. This paper explores technology that provides control over the extent to which inter-address-space communication is exposed to programmers, in order to aid the creation, maintenance and evolution of distributed applications. The described system permits arbitrary objects in an application to be dynamically exposed for remote access, allowing applications to be written without concern for distribution. Programmers can conceal or expose the distributed nature of applications as required, permitting object placement and distribution boundaries to be decided late in the design cycle and even dynamically. Inter-address-space parameter passing semantics may also be decided independently of object implementation and at varying times in the design cycle, again possibly as late as run-time. Furthermore, transmission policy may be defined on a per-class, per-method or per-parameter basis, maximizing plasticity. This flexibility is of utility in the development of new distributed applications, and the creation of management and monitoring infrastructures for existing applications.Comment: Submitted to EuroSys 200

Using a Commercial Framework to Implement and Enhance the IEEE 1451.1 Standard

In 1999, the 1451.1 Std was published defining a common object model and interface specification to develop open, multi-vendor distributed measurement and control systems. However, despite the well-known advantages of the model, few have been the initiatives to implement it. In this paper we describe the implementation of a NCAP – Network Capable Application Processor, in a well-known and well-proven infrastructure: the Microsoft .NET Framework. The choice of a commercial framework was part of our strategy: to take advantage of several “of the shelf” technologies and adapt them to produce a NCAP prototype, called NCAP/XML. In addition, a solution to enhance the 1451.1 Std is presented by proposing a new format for inter-NCAP communication based on XML (eXtended Markup Language)

Plataformas Middleware comerciales para la integración de flujos de vídeo bruto

El documento realiza un estudio sobre el uso de distintos componentes COTS (Comercial Off-The-Shelf) dirigido al desarrollo de aplicaciones que hagan posible la integración de flujos de vídeo. El objetivo es presentar tres plataformas de integración (CORBA, JavaRMI y .Net Remoting) que permitan construir aplicaciones y servicios distribuidos para transmitir y recibir flujos de vídeo sin compresión. CORBA y dentro de este, aquellos ORB’s que incorporen entre sus servicios el denominado A/V Stream, hace posible la implementación de este tipo de aplicaciones. JavaRMI y más recientemente .Net Remoting son dos plataformas que permiten el desarrollo de aplicaciones distribuidas multimedia, pero con limitaciones propias: en el caso de JavaRMI, el lenguaje de programación (Java) y en el caso de .Net Remoting, el sistema operativo (Windows).Escuela Técnica Superior de Ingeniería de Telecomunicació

Building a Truly Distributed Constraint Solver with JADE

Real life problems such as scheduling meeting between people at different locations can be modelled as distributed Constraint Satisfaction Problems (CSPs). Suitable and satisfactory solutions can then be found using constraint satisfaction algorithms which can be exhaustive (backtracking) or otherwise (local search). However, most research in this area tested their algorithms by simulation on a single PC with a single program entry point. The main contribution of our work is the design and implementation of a truly distributed constraint solver based on a local search algorithm using Java Agent DEvelopment framework (JADE) to enable communication between agents on different machines. Particularly, we discuss design and implementation issues related to truly distributed constraint solver which might not be critical when simulated on a single machine. Evaluation results indicate that our truly distributed constraint solver works well within the observed limitations when tested with various distributed CSPs. Our application can also incorporate any constraint solving algorithm with little modifications.Comment: 7 page

Pembuatan System Corporate Messenger Pada Jaringan Lan

Corporate messenger is the one of the application that can be used for communication in a local area network. The backgrounds of this topic are needs of sending message process in the LAN. The messages which want to be presented are not only in a text format, but also can be in audio visual format. Computer client will connect to the server. When the connection has been established, the client continued the authentication and started sending message between client and server. Audio and video message sending can be done with peer to peer connection with entering the IP address first from remote user that we want to communicate with. The evaluation of this application was done by using 3 computers and as the result, we found that authentication process can work properly, sending text message was done properly and communication using audio can be heard clearly. In addition to video sending message, we could see directly in remote client. The average time to show the video on remote client is 3.771 seconds

IEEE 1451.1 Standard and XML Web Services: a Powerful Combination to Build Distributed Measurement and Control Systems

In 2005, we presented the NCAP/XML, a prototype of NCAP (Network Capable Application Processor) that runs under the .NET Framework and makes available its functionality through a set of Web Services using XML (eXtended Markup Language). Giving continuity to this project, it is time to explain how to use the NCAP/XML to build a Distributed Measurement and Control System (DMCS) compliant with the 1451.1 Std. This paper is divided in two main parts: in the first part, we present the new software architecture of NCAP/XML (which suffered some changes since the first version), and secondly, we describe the network configuration of a Web-enabled DMCS, which includes several NCAP/XML stations, a database and a Web Server