|
Distributed Object Oriented
To View implementation and Java doc click here Description : Here we use N number of counters to implement tie and implementation approach of CORBA. Counter is taken as data structure of ORBIX(version 3.0 for Java) as sequence or array of long datatype of size N. For each counter ,there are the operation to initialize the counter to a given value k, Increment the value of the counter by value m, retrieve the values for each counter and dump the counter (using Holder classes for the array and sequence).This is totally menu driven. Application will launch the server by itself and you can perform various operation on it. Exception handling is used for incorrect clients. It is implemented by using both tie and implementation approach. To View Report and Presentation click here. This is a simple bank application to debit and credit transaction for the banking machine.This is to demonstrate the use of CORBA with JDBC. This is a small application which is using two Protocols CORBA and JDBC. It has a multithreaded client. Each client thread coordinated with the server as well as the database. In this main client thread we creates two threads database thread and callback threads. Database thread established a connection to the database and callback thread is used to listen to the server for the callbacks. There is a multiconsole applet(server side code) which is coordinating the server. The multiconsole applet uses CORBA to connect to the server. Multiconsole Applet is sending request to the server to start the transaction. Now the server which was listen by the callback thread send the request to this thread at the client side which transfer this request to the database thread to start the execution on the MS ACCESS database and start listening back to the server. So this is a totally multithreaded scenario using CORBA, JDBC and callbacks.To view Java documentation click here Description: In this we create a framework in which a student (a client) can use an applet or application to displays her/his marks (for multiple courses). This applet is automatically updated (using callbacks) when ever there is a change in students marks from the server. Each student has its ID and password to login to the system. Administrator can also login but it has more privilege then the student. Administrator can add, selete and modify student information such as course he/she is registered, marks for these courses and password etc. Persistence of the object is using file. If you want to Shut down the server then everything is saved into the file. |