service-oriented application can be negatively affected by a variety of factors. Network volatility, hostile exploits, poor service management, all can prevent a service-oriented application from delivering its functionality to the user. This paper puts forward a novel approach to improving the reliability, security, and availability of service-oriented applications. To counter service vulnerabilities, a special service detects vulnerabilities as they emerge at runtime, and then hardens the applications by dy-namically deploying special components. The novelty of our approach lies in using a declarative framework to express both vulnerabilities and hardening strategies in a domain-specific language, independent of the service infrastructure in place. Thus, our approach will make it possible to harden service-oriented applications in a disciplined and systematic fashion. I.

Pour obtenir le grade de

During 2008 I was researching in the “usual way ” within the Innovation department of my company. That was the period of a deep transformation from Research to Innovation. At that time, researchers were put within very confined and limited terrains to explore. It was a sort of intellectual “prison ” that many Operators were constructing in order to tackle the challenges of the Web world. Instead of opening up minds and research, the approach was to leverage the assets and competitive advantages of the Operators. This approach was aggravating even more the “attitude ” of Operators to feel better and more capable of other Competitors. I felt a compelling need to break these glass walls and breath fresh air. On the other side, the success of Web Companies was so stimulating and challenging that there was (is) the need to understand how to build the future of communication service. One thing was puzzling me: how much the needs and rights of users were disregarded. So I decided to put on my “User Hat ” and figure out if a more user centric web was possible. This was the main personal motivation to enter in a Doctorate.

Origine et développement des cellules germinales chez l’hûıtre Crassostrea gigas: intérêt pour le contrôle de la reproduction en écloserie

Abstract Due to the shift from software-as-a-product (SaaP) to software-as-a-service (SaaS), software components that were developed to run in a single address space must increasingly be accessed remotely across the network. Distribution middleware is frequently used to facilitate this transition. Yet a range of middleware platforms exist, and there are few existing guidelines to help the programmer choose an appropriate middleware platform to achieve desired goals for performance, conciseness, intuitiveness, and reliability. To address this limitation, in this article, we describe a case study of transitioning an Open Service Gateway Initiative (OSGi) service from local to remote access. In our case study, we evaluate five remote versions of this service, constructed using different distribution middleware platforms. These platforms are implemented by widely-used commercial technologies or have been proposed as improvements on the state of the art. In particular, we implemented a service-oriented version of our own Remote Batch Invocation abstraction. We compare and contrast these implementations in terms of their respective performance, conciseness, complexity, and reliability. Our results can help remote service