Use case example

System offers few functionalities but most of them communicate in the same way.


Above diagram show way in which client save data to the database and receive version on which ther were saved

1,2 - client application requests for data manager from Database Access Provider(DAP). DAP return cached instance of manager or new one in case that there is no cached instance.
3 - application call method on manager in order to perform save action
3.1 - manager using ICE marshall data to byte stream and send it to the server side. After unmarshaling request, between 4th and 5th step server converts data to the database structures.
3.1.1 - 3.1.2 - server's object request for DAO which procide functionality to save given type of data. DAOProvider return cached to the requester or new one in case that there is no cached one.
3.1.3 - manager implementation invoke method on DAO object to save data. - thanks to the JDBC data is sended to the database. - database return to the DAO object version on which data was send.
3.1.4 - object responsible for accessing data return version of the data to the manager implementation.
3.2 - manager marshall reply from DAO and send it to the client side.
4 - client application gets version of data which saved.

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2012-09-12 - unknown
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    TOTEM All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback