4 ms·

I should say it was 3 years before RFC 2068 (2616 superseded). When Microsoft came out with their extension, and then it eventually ended up in HTTP/1.1 (or at

I should say it was 3 years before RFC 2068 (2616 superseded). When Microsoft came out with their extension, and then it eventually ended up in HTTP/1.1 (or at least some version of it), we pivoted to a primarily client-side product that offered read-ahead caching, metasearch (could perform a query on multiple search engines like Hotbot, Altavista, Infoseek, etc. -- this was pre-Google) and save and integrate the results. It would also then rerun those queries periodically and highlight new results, and you could save or bookmark. We also used that search technology in a product that would monitor trademark use, which companies used to keep track of where and how their trademarks or brand names were being used. We never made enough to keep that side of the business running, while the web consulting/development side grew and grew. These were pre-2000 days when businesses were wanting to "get online".

tpmx 3y ago
Would you be able to share any more details on the startup - privacy allowing? What tech were you using on the client (Windows 3.x/95?)/server-side? Did WebTV/MSN TV do anything of this? (Fascinated with early HTTP/web optimization tech because of my part in creating the much later Opera Mini - launched mid 2005.)
- acegopher 3y ago
  Sure thing! I was on the client-side, and joined in 1995, when there was already a version 1 of the compression/connection piece. I started work and was lead on the search product. If I remember correctly, we were developing on Windows 3.1 with Microsoft Visual C/C++ 7.0 to start and then moved to Windows 95 and Visual C++. We used Microsoft Foundation Classes, as well as Rogue Wave libraries (tools.h++ I believe). We were funded by some guys who had made a lot of money in government software contracts (we were near a major Airforce base). Here is a Google folder link with some scans of contemporaneous ads and press coverage: https://drive.google.com/drive/folders/0BzleZlz4NcDSMDc0VTBpdG9uU3c?resourcekey=0-qS2PqIhUXs0XzuUKh1jlSA&usp=share_link https://drive.google.com/drive/folders/0BzleZlz4NcDSMDc0VTBp...
  - tpmx 3y ago
    Brilliant, thanks! (For future readers: The product name was Blaze Web Performance Pack, offered by Datalytics Inc, Dayton, Ohio. They used the domain speeditup.com in some ads.)

tpmx 3y ago

Would you be able to share any more details on the startup - privacy allowing? What tech were you using on the client (Windows 3.x/95?)/server-side? Did WebTV/MSN TV do anything of this? (Fascinated with early HTTP/web optimization tech because of my part in creating the much later Opera Mini - launched mid 2005.)

acegopher 3y ago
Sure thing! I was on the client-side, and joined in 1995, when there was already a version 1 of the compression/connection piece. I started work and was lead on the search product. If I remember correctly, we were developing on Windows 3.1 with Microsoft Visual C/C++ 7.0 to start and then moved to Windows 95 and Visual C++. We used Microsoft Foundation Classes, as well as Rogue Wave libraries (tools.h++ I believe). We were funded by some guys who had made a lot of money in government software contracts (we were near a major Airforce base). Here is a Google folder link with some scans of contemporaneous ads and press coverage: https://drive.google.com/drive/folders/0BzleZlz4NcDSMDc0VTBpdG9uU3c?resourcekey=0-qS2PqIhUXs0XzuUKh1jlSA&usp=share_link https://drive.google.com/drive/folders/0BzleZlz4NcDSMDc0VTBp...
- tpmx 3y ago
  Brilliant, thanks! (For future readers: The product name was Blaze Web Performance Pack, offered by Datalytics Inc, Dayton, Ohio. They used the domain speeditup.com in some ads.)