The current stand-alone applicaiton is written in Java for windows OS. We are looking to do some visual upgrades to the look of the current application while keeping the internal functionality the same. We have the graphics and visuals for how we want the new application to look. If you can also write a native language for MAC OS there may be another opportunity after this one is complete--a MAC version of this same application.
We desire to replace a Java Bidder application and a linked Delphi based stream Player with a single executable (Windows & MAC versions), utilizing a new, fresh /user Interface that we've already designed.
BidLive allows a traditional Auction House to transmit an auction to Bidders worldwide. From a network perspective, it consists of two major, independent channels, the actual bidding activity, and, separate from that, live audio & video from the auction site.
There are several distinct applications involved:
1. A Clerking desktop application (Java)
2. A Bidding server (Java)
3. A Bidder or client desktop application (Java)
4. A Desktop media streaming Transmitter application (Visual Basic)
5. A streaming media server (Java)
6. A streaming media desktop Player (Delphi)
This services live auctions that proceed at a very rapid pace. It is so fast that we cannot allow any kind of buffering in the streams.
The entire package has been working flawlessly for a long time. For this software update, we are not looking to add any new function, merely replicate what already exists in the Bidder.
For network communications, we use TCP (for reliability) for the actual bidding process, and UDP for the streaming audio & video.
Bidder - to replace the current Java based Bidder with a standard Windows and MAC executable The Bidder communicates with the BidLive server, receiving various short messages (from the auction clerk) and sending back login information and any bids made by the customer.
Desktop Media Player - this exists as a separate Delphi application today. We will want that melded into the new Bidder code. It receives and plays back audio / video transmitted from the auction house, via UDP & the BidLive server.
You will likely also replace the current stream source, or Transmitter, to match whatever new codecs,etc.may be used
The Bidder portion is fairly straight forward, login, etc., and being capable to receive a fixed set of TCP messages from the Server, respond to the Bid button, and constantly update the user's window as the auction progresses.
Because of the rapid auction pace, delivering the real-time stream will be the greatest challenge. There will be NO buffering or use of overlaying protocols (e.g. RTSP, etc.). We anticipate using codecs (audio & video) with the best compression ratios, smallest packet sizes.
The first step for our developer will be to demonstrate the live streaming, equal to at least the current performance we have today. Ladies & gentlemen, our application is absolutely dependent on the rapid streaming. If you are not competent in this area, please don't apply. Beyond that, the actual bidding process is very simple messaging and UI updating
Here is a picture of how our streaming process works: http://ebidlive.com/BidLive_Stream_Process.jpg
Here is a picture of how our Auction process works:
What we want the new bidder to look like can be found in the attached section of this document. The older version has very similar characteristics except it looks like its about a decade old.
There are no clarification questions.
The Case Study is a short task that is a taste of what the full Job will be like and
gives you the opportunity to show the Buyers your skills.
Keep in mind that you have more chances to win a Job with Case Study as fewer Sellers will send a proposal.
Moreover the Buyer has already paid a fee for it, which shows that they seriously intend to award the Job.