Internet Explorer Browser Helper Object

Great Windows programmer needed for IE BHO (plugin). Visual C++ ATL Project or possibly C# .NET. (This link to Google Doc document is easier to read: <[login to view URL]>) **Brief** We need a BHO (extension) for IE. The basic functionality is an Alexa clone ([login to view URL]) without the toolbar and just the logging ability. Compabilty with IE8, IE9, IE10. Win xp, win vista, win7. Both 32 and 64 bit. Swedish and English OS. For every pageview the user does an additional request is made to one of our servers. Example: 1. User visits [login to view URL] 2. BHO will do a http post to https://<server>/send_data with these parameters: 1. username 2. password 3. identification_code (unique code to identify browser) 4. url visited ([login to view URL]) 5. referring pageview. what was the previous url? 6. type of visit 1. typed in url bar 2. bookmark 3. link 4. startpage 5. all (possible) transition types by google (<[login to view URL]>) The user will have an account to log into. The application makes it possible for users to log their browsing history to a server. An installer will, except from installing BHO, install Chrome and Firefox plugin (provided by us). ## Deliverables (This link to Google Doc document is much easier to read: <[login to view URL]>) _____________________________________________ Great Windows programmer needed for IE BHO (plugin). Visual C++ ATL Project or possibly C# .NET. ** Brief** We need a BHO (extension) for IE. The basic functionality is an Alexa clone ([login to view URL]) without the toolbar and just the logging ability. Compabilty with IE8, IE9, IE10. Win xp, win vista, win7. Both 32 and 64 bit. Swedish and English OS. For every pageview the user does an additional request is made to one of our servers. Example: User visits [login to view URL] BHO will do a http post to https://<server>/send_data with these parameters: username password identification_code (unique code to identify browser) url visited ([login to view URL]) referring pageview. what was the previous url? type of visit typed in url bar bookmark link startpage all (possible) transition types by google The user will have an account to log into. The application makes it possible for users to log their browsing history to a server. An installer will, except from installing BHO, install Chrome and Firefox plugin (provided by us). **Some requirement** Installation file will also include installation of Chrome and Firefox extension. The installation file will install the IE BHO (that you develop) + additional browser plugins we have developed. That way the user will have the same plugin cross browser. In the installation process username and password will be asked for. This information will copied to the plugins (ie, chrome, ff). User will type username and password once in the installation and not for every plugin. Installation mockup. The IE BHO will run in background. Toolbar is not needed. Menu item to change login credentials. User will be able to change to another account from an options page. IE BHO will have performance as Alexa Toolbar. No impact on navigation or startup speed. Request to our server will be done after the page is rendered. Navigation and startup speed under 0.05 s. Automatic update of BHO. Users shall not have to re-install or submitt user name or password unless they themselves log out of the BHO. Compabilty with IE8, IE9, IE10. Win xp, win vista, win7. Both 32 and 64 bit. Swedish and English OS. ** Complete user experience ** To better understand the process for our users. User creates account on [login to view URL] To validate email address an email is sent. When the user click on the link to verify email he gets to a page where he can download the plugin installer (You create this installer). User inputs username and password (from registration) The installer checks for installed browsers: IE, Chrome and Firefox. The installer will install IE BHO (your plugin), Chrome plugin and Firefox plugin. We have chrome and FF-plugin. Installation mockup is available here. The installer will (as agreed) save user credentials to the plugins directly from installer. Right now Chrome saves credentials in html5 storage. FF saves them in the their Preference Manager. We can make small modifications on where to save this if necessary. (You do not have to worry about Chrome and FF from now on if they are correctly installed). When the IE BHO starts for the first time it will check if user credentials are ok with remote_login ([login to view URL]). Create random identification_code (random md5). Use function or [login to view URL] or do it in the BHO. On first run call new_gatherer ([login to view URL]) with the new identification_code. Extension_version = 2.0 and browser_name = IE <version number>. Now everything is ready to start logging pageviews. After every pageview call log_pageview ([login to view URL]). Transitions are described by google. Perhaps not all of them are possible to implement. When an plugin update is done step 8 and 9 are called again to create a new gatherer (extension_version=2.1). The user can change credentials from menu. If credentials are changed step 8 and 9 needs to be repeated. **Development** Use VM to test in every environment. It is probably the easiest way to debug. You will have to use your own development environment. Use some sort of versioning system. I recommend mercurial and a private repository on Bitbucket (it is free). Makes it easy to get source between test computers. [login to view URL] We have more projects like this in the near future. A well done job will most likely result in additional projects.