190069 Human Captcha Entry System

Either VB or .NET, not necessarily both. - Microsoft windows compatible - Set in system tray and reduce itself to the system tray when not in use. Shut down should only be possible from right click on system tray icon. It should also be added to the system startup on installation. - Screen will display a message area when messages need to be shared with the user. Most common display will show an image that can be found on the Internet, a textbox for value entry and one or two buttons (submit/new request and cancel) - The system must mimic a known web-browser (i.e. msie) when speaking with the target website. In addition we may be required to support cookies and provide specific values for environment variables (referrer, user-agent, etc) This system is a bridge between two websites referred to below as “our website” and “target website” and the local computer which the system is operating on. In general the system must request instructions from our website, utilize those instructions to make a series of requests to the target website, and send the target website's response back to our website. 1. Make a request to our website 2. Our website will respond with one of two responses in XML 2a. no requests present & a time to wait before asking again If this response is received the software should minimize to the system tray (or stay minimized if it is already so) and set a countdown timer for the next request to our website. 2b. a set of xml requests to be processed If this response is received the software must complete the remaining steps. 3. Process a login request to the target website. - if the login fails send a “login failed” status message back to our website - if the login is successful continue the request 4. Request a second page that has a captcha image on it. The page source code must be processed to capture the source url for the captcha image (changes with a variable) 5. Request that captcha image from the source url captured in step 4 and display that image to the software user. Software screen should be displayed and brought into focus if necessary. 6. The user now enters a value for the captcha image into a textbox on the software and submits that image to the software, not a website. 7. The software prepares a request for the target website and submits that request, then waits for a response. 8. When a response webpage is received from the target website the pages source must be parsed to determine what that response means. A successful response, as well as a few failed responses must be submitted back to our website in provided xml formats. At which time new requests will be issued if available. Steps 7 and 8 may be held in a queue and performed at a preset time if the target website's system will allow such a queue to work. We should consider other ways in which we could speed up the number of requests one system could make at a given time. For example, using threads. I will provide the xml schematics and the php script that the local windows based application will work with. Our target website only has requests for us to process at special times and we need to time these requests to occur as closely to the earliest time as possible. Right now those times are Wed through Saturday for the next few weeks. Then, we will be stuck in a holding pattern until sometime probably in mid November. So, speed and commitment are required for this project. This should be a simple project for the right programmer, requiring less than 15 hours I would guess. Target website information will be provided to programmers that are being considered. You must also agree to the following: - You will provide regular daily updates on the project Monday through Friday. Should you not communicate with me for a period of more than three consecutive week days you agree that the escrow agency can immediately refund any deposited funds to me upon my request.