Browser Helper Object

1. Communications: This going to serve as the primary communication layer between an executable running as a service and a webserver. The component must be able to communicate via http over port 80 (possibly 443) using the standard POST model. 2. Installation, Operation, and API Requirements Installation will require the user to allow Active X controls to run within the IE environment, as well as the ability to communicate to the system service mentioned in item one via named pipes. The package must be installable via a download, and have the ability to address the System Service API (gethash, isalive). The user will interact with the system via the control embedded on an IE form. Below is a sample of what the elements of the form will contain. Login Page: Username: (field) Password: (field) (submit button) ## 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). ## Platform An Internet Explorer component to reside as an Active X. I am open to using an alternatives like a java applet etc.