Mario Noioso

Actual business is continuously changing and requires application used to manage the business to change accordingly in a rapid and often unachievable way. A system managing software license of products is often based on instrumental code wired in software product or by the handle of start and stop events of the product to monitor for licences puropose. Moreover the current licensing system doesn't allow a fine-grainded event to license. ForActual business is continuously changing and requires… Visualizza altro

Actual business is continuously changing and requires application used to manage the business to change accordingly in a rapid and often unachievable way. A system managing software license of products is often based on instrumental code wired in software product or by the handle of start and stop events of the product to monitor for licences puropose. Moreover the current licensing system doesn't allow a fine-grainded event to license. ForActual business is continuously changing and requires application used to manage the business to change accordingly in a rapid and often unachievable way. A system managing software license of products is often based on instrumental code wired in software product or by the handle of start and stop events of the product to monitor for licences puropose. Moreover the current licensing system doesn't allow a fine-grainded event to license. For example it is possible to handle the license for a start or stop of an application but is not possible monitoring the license for a database transaction inside the application. The scope of this publish is show a new licencing approach for j2ee application that lives in Websphere server. example it is possible to handle the license for a start or stop of an application but is not possible monitoring the license for a database transaction inside the application. The scope of this publish is show a new licencing approach for j2ee application that lives in Websphere server. Meno dettagli

A solution for metering usage of at least one software product on a data processing system, the at least one software product having a plurality of available associated licenses, each license having a set of attributes. An event indicative of the use of the at least one product on the system is detected. Responsive to the detection, the best available license among said plurality of licenses is determined according to predetermined preference rules of the attributes. Metering conditions to the… Visualizza altro

A solution for metering usage of at least one software product on a data processing system, the at least one software product having a plurality of available associated licenses, each license having a set of attributes. An event indicative of the use of the at least one product on the system is detected. Responsive to the detection, the best available license among said plurality of licenses is determined according to predetermined preference rules of the attributes. Metering conditions to the at least one software product are applied according to the identified best available license. A change of the best available license is detected. New metering conditions are applied to the at least one software product accordingly. Meno dettagli

Some software applications use the geographical position of a computer to offer some services bound to the physical location where the client runs. Existing applications are usually based either on user-input or on IP Address to determine such position. This paper aims at extending the current solutions to a more reliable and friendly one, implemented by a combination of hardware (GPS system) and software.

Main idea should help an operating system user to access to different virtual OS running on the same physical machine. Actually on a physical machine can run different virtual OS, some of them are a share/portion of native os (i.e. vncserver), others are new os running in a visualizer machine (i.e vmware). An user accesses to vncserver by native client (vncviewer) or webclient, otherwise for vmware the user can access on virtualize machine only by phisical machine, or same NAT complex… Visualizza altro

Main idea should help an operating system user to access to different virtual OS running on the same physical machine. Actually on a physical machine can run different virtual OS, some of them are a share/portion of native os (i.e. vncserver), others are new os running in a visualizer machine (i.e vmware). An user accesses to vncserver by native client (vncviewer) or webclient, otherwise for vmware the user can access on virtualize machine only by phisical machine, or same NAT complex redirections. To provide an unique solution for this problem a Virtual Access Point (VAP) can be usefull.

This solution consists of a software layer running on top all virtual servers, a virtual access point.
With this solution client connects to virtual access point and choose the virtual OS to use. Meno dettagli

In a client-service architecture, a server application can use information about its own state and the client's request to choose between different implementation flavours of the same service. The implemented flavours differ for the level of information provided to the calling clients. This is because the more the service is tailored to the needs of the client, the higher is the server processing cost and the lower is the client one. Conversely, if the service is too generic, and does not… Visualizza altro

In a client-service architecture, a server application can use information about its own state and the client's request to choose between different implementation flavours of the same service. The implemented flavours differ for the level of information provided to the calling clients. This is because the more the service is tailored to the needs of the client, the higher is the server processing cost and the lower is the client one. Conversely, if the service is too generic, and does not address the client's specific requirements, the server processing tends to be low while the client one may be high.

Therefore, it is possible to define different implementations of the same service to move the processing from the server to the client depending on the server workload. If the workload of the server is high, the server can use a light solution based on algorithms that use less server resources, but with less "precision" in the service response. This means for instance that if the service is a request for an information update, the amount of information sent to the client may not be exactly tailored to the client's needs, and some information that the client already knows may be sent again. In this case the service elapsed time on the server is reduced, but the service is not tailored to the requesting client, which may need to apply a specific processing to adapt the results of the service to its special needs. On the other hand, if the workload of the server is low, the server can apply more processing to provide a service response that is completely tailored to the client needs, reducing the time required to process this response on the client itself. Workload thresholds can be used to define the service mode to be used when addressing a client request.... Meno dettagli

The IDEs client is connected to central repository as usual, but in this architecture the source code repository server and the IDEs client should use a bus to communicate the changes on source code tree. For example if a developer chechs-in a source file after some changes the source code server produces a message on the bus. The other IDEs client are listening on the bus and they will get the message produced by server, then this message will be notified to developers in IDE environment… Visualizza altro

The IDEs client is connected to central repository as usual, but in this architecture the source code repository server and the IDEs client should use a bus to communicate the changes on source code tree. For example if a developer chechs-in a source file after some changes the source code server produces a message on the bus. The other IDEs client are listening on the bus and they will get the message produced by server, then this message will be notified to developers in IDE environment during normal developer work. In this way all developers will be always updated about all code's changes without manual refresh of source code tree. Meno dettagli