Show Bid Request
1/26/2003 open bid JAVA-corba
Bid Request Id: 45155
|
|
|
|
Posted by: |
JGRoch (1 ratings)
(Software buyer rating 10 )
|
|
Non-action Ratio: |
Very Good - 0.00%
|
|
Posted: |
Jan 24, 2003
12:56:10 PM EDT
|
|
Bidding Closes: |
Feb 7, 2003
12:59:56 PM EDT
|
|
Viewed (by coders): |
61 times
|
|
Deadline: |
2/24/2003
TIME EXPIRED
|
|
|
|
|
Description:
This homework will give you a chance to write a small distributed program using CORBA. Although your finished product should work when the processes are run on different systems, to keep things simple you may test it on a single machine. The basic idea is to produce a simple system, consisting of three processes, which manages a single auction.
The first process is the Manager process. It keeps track of the current high bid, the name of the current high bidder, and the total number of bids. The Manager is not required to produce any output, although you may want to do so for testing and debugging purposes.
The second process is the Monitor process. It runs as a client to the Manager, and can request the current status. When it does, the Manager returns the three pieces of information described above. The Monitor should then display the info. (You can use either a GUI or just write to stdout.)
The third process is the Bidder process. This also runs as a client to the Manager. The Bidder sends a bid amount and a bidder name to the Manager. (The Bidder should obtain these from the command line, to make it easy to test your system.) The manager returns either "true" or "false", to indicate whether the bid amount is high enough to be the new high bid. A new Bidder process is run for each bid made, i.e. the process simply makes the bid and then exits.
Whenever a new high bid is submitted, the Manager must update its state appropriately.
Decide what your interface(s) should look like, then write them in IDL. Include at least two CORBA operations (Java methods), one for the Bidder to use and one for the Monitor to use. Test your system to make sure it works correctly. (To start a new auction, just shut down and restart the Manager process.)
code from the class examples, including the simple naming service wrapper. I encourage you to look over these class examples carefully, as virtually everything you need for this assignment is in on need idl & JAva
Deliverables:
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Installation package that will install the software (in ready-to-run condition) on the platform(s) specified in this bid request.
3) Complete ownership and distribution copyrights to all work purchased.
Platform:
JAVA-Corba-idl
Must be 100% finished and received by buyer on:
Feb 24, 2003 EDT
Deadline legal notes: All times are expressed in the time zone of the site EDT (UT - 5). If the buyer omitted a time, then the deadline is 11:59:59 PM EDT on the indicated date.
Special Conditions / Other:
This is a homework assignment I can not get to work it is due today..01/26/03. Please let me know if you can do it.. there is a second part.
Modify your three processes so that the clients stay connected to the server, and the server notifies them whenever there is a relevant change in status:
After a bidding client makes a bid, the client process will wait for a callback from the manager. The first time anyone else bids higher, the manager will notify the client by making a callback.
When an admin client connects, the manager will send the current status, but it will re-send the updated status whenever the status changes (i.e. whenever anyone makes another bid).
The logic of deciding on who has the current high bid will not change, but you will need to modify your interfaces in the IDL file. You will also need to modify all three processes (two clients and the server) to use your revised interface descriptions.
If you wish, you may use code from the Sample Solution to
Remember that contacting the other party outside of the site (by email, phone, etc.) on all business projects < $500 (before the buyer's money is escrowed) is a violation of both the software buyer and seller agreements.
We monitor all site activity for such violations and can instantly expel transgressers on the spot, so we thank you in advance for your cooperation.
If you notice a violation please help out the site and report it. Thanks for your help.
|
|
|
Bidding/Comments:
|
All monetary amounts on the site are in United States dollars.
Rent a Coder is a closed auction, so coders can only see their own bids and comments. Buyers can view every posting made on their bid requests. |
See all rejected bids (and all comments)
| Name |
Bid Amount
|
Date |
Coder Rating |
|
|
This bid was accepted by the buyer!
|
$20 (USD)
|
Jan 26, 2003
6:43:33 AM EDT
|
10
(Excellent)
|
|
|
Hi,
I've coded distributed systems before. I can do it today but I should start... well... today!
Regards,
Guntis
|
|
|
|
|
|
|
