Java Reference
In-Depth Information
e.printStackTrace();
return null
;
}
}
public
Proposal finalProposal(){
return
negotiator.finalProposal();
}
}
20.6.4
Test
The test for this application is based on the same test cases as the previous
prototype. The only difference is that now three different processes must be
started, possibly on different computers connected through a network.
It is important to set the names of the machines in order to allow the MMI
framework to find the distributed objects correctly.
20.7
■
Extension
The previous prototype worked on the assumption that multiple requests
from service clients are serialized. In reality this could be too heavy a
restriction. Therefore the system should be extended to allow multiple
concurrent negotiations to be carried on.
It is important to be able to interrupt or restart a negotiation when
another successful negotiation reserves a resource and modifies both the
availability and the provider's preferences.
20.8
■
Assessment
Domain analysis
. The need for a general-purpose negotiation service moti-
vated the development of this framework. The analysis of the domain started
from the literature using a top-down approach.
Scope
. Negotiation is a typical horizontal service that can be used in
several domains, ranging from optimization to e-commerce. Domain-specific
negotiation services can be developed by customizing the negotiation frame-
work. The scope of this framework can be classified as a service.
Customization
. The framework offers two levels of customization. At
the first level it is possible to define the domain-specific semantics, which
consists of the attributes and their possible values. At a further level it is
possible to select specific negotiator classes that implement different
negotiation policies. At both levels the customization can be classified as
grey box.
