Enterprize screen capture
$500-5000 USD
Płatność przy odbiorze
This product will consist of 3 parts:
Client - captures screen images, and sends them to the Server.
Viewer - shows captured images
Server - manages images and Client configuration.
Please see attached document.
This product is intended for re-sale. So installation is also required.
## Deliverables
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
* * *This broadcast message was sent to all bidders on Saturday Dec 8, 2007 5:53:29 PM:
Hi, I've extended the bid date. I have also greatly expanded the description of the project. If you are interested, please read the following, and bid. Regards Michael. ======================= There are 3 parts to this project. *** Client ***. Runs as a Windows Service. Needs basic GUI (simple configuration screen). Parameters stored in .INI or .XML file. Each Client can be configured with different Parameters. These parameters can reside either locally, or on the Server (to be determined). If they reside on the Server, the Client will still need to store Server’s address/port information. These Parameters are: Server address/port (to be discussed. We need to take into the account various network security configurations to enable the transmission of images to the Server) Client ID (default PC name) Frequency (how often to capture screen image, default every 5 seconds) Resolution (default to client’ screen resolution) From hour (default 08:30) To hour (default 17:30) Days of Week (default Mon thru Fri) Provide ability to identify Holidays (don’t send on these days) Client sends full screen images to the Server. Client software should be able to suppress transmission of the image if there are no changes on the screen. Client software must be able to accept change in the parameters from Server (or have Client periodically look up corresponding parameters on the Server, and make appropriate changes). Frequency of screen capture can be changed by the Viewer (thru the Server). Important to chose image format (JPEG, PNG, or open to suggestions) that uses the least bandwidth. It is possible to create a “pseudo- real-time?? by setting Frequency to 1 second. Obviously, this will create a very large number of files, and if many Clients have this setting, it could affect the network performance. The captured images should be transmitted to the Server as soon as possible. If the Server is unavailable, store images locally until can transmit to the Server. When re-transmitting, don’t send everything at once. Do it in “chunks?? with a 5 second interval. If Free disk space on the Client PC falls below 5 GB, replace Old images with the New. Each image will follow this naming convention: ClientID_YYYYMMDD_HHMMSS. ext (JPEG, PNG, or …..) *** Viewer ***. A stand alone application that will display screen image of selected Client. These images are stored by the Server prior to the Viewer being able to get to them. This application could be either Web-based or not. There could be multiple Viewers launched from different PCs, and, possibly, from the same PC. There needs to be a “basic?? secure login: user id and password. These fields would be set up in the Server configuration. The Viewer should be able to run in two modes. In a “stand alone?? mode, the Viewer will display a list of available Clients. Must be able to accommodate a large number of Clients (a scroll list?...). To select a Client, right-click on it. A pop-up will display options: Change Client settings; Show activity ( like a “slide show??); Copy a range of images (Allow to select a range of sequential images From date/time ??" To date/time, and copy them elsewhere). If Change Client settings selected, the User will be able to update individual Settings on a particular Client PC. Somewhere on the Viewer there needs to be an option to Set All Clients parameters. When starting a “slide show??, allow to enter Date and Start time (by default, display the most current image). Offer “navigational?? controls (REW, FWD, PAUSE, STOP, etc..). Also, allow Faster or Slower speed of the slide show. The second mode will allow the Viewer to be “called?? from a Web report (we have a Web application that will “call?? the Viewer, and pass it the name of the Client, Date and Start Time). If “called??, the Viewer will immediately go in to “slide show?? mode for the Client, using Date and Start Time. Offer Navigation controls as above. The following is true for both modes. When viewing an individual screen image, you can click PAUSE to “pause?? the “slide show??. During the “pause?? period, allow this image to be saved and/or e-mailed. Click PAUSE again to resume the “slide show??. *** Server ***. Runs as Windows Service. There needs to be a “basic?? secure login: user id and password. Default: “admin/admin123??. Somewhere in the GUI for the Server allow for these fields modification. How the Server receives images from Clients, needs to be determined further. Network and security issues need to be taken in to consideration. Should we use any port or HTTP? All suggestions are welcome at this time. Obviously, the least impact on Network configuration is most preferable. Receives images from Clients, and stores them either in files or DB (if using DB, will use MS SQL Express). Since we could be dealing with a Very large number of files, we need to discuss it further. Server can reset a specific Client or ALL Clients’ parameters (requested via Viewer).. Server will be able to Archive/Delete images automatically. You could specify different number of days to “store?? for different Clients. After a “set number?? of days, images will either be Deleted, or Archived (moved to another location specified by user). Server will also have ability to Import previously Archived images. Will need a GUI to specify this information. Will provide all relevant Client information to the Viewer.
## Platform
This application is intended for Windows platforms.
Numer ID Projektu: #3514929
O projekcie
15 freelancerów złożyło ofertę za $2815 w tym projekcie
