The cloud wars will pick two camps against each others: on one side, advocates of applications running on the desktop; on the other advocates of applications running in a browser.
I’ve been working on cleaning up my webalizer.conf file in order to get better statistics. Since I haven’t seen anyone posting the following information, I figured I would, since it might interest people who are using the Webalizer stats tool. Adding the following lines to your webalizer configuration file (webalizer.conf) will allow you to get much cleaner reporting of user-agents. GroupAgent Check&Get Program: Check&Get (Bookmark Manager) GroupAgent eXactSite Program: eXactSite (HTML authoring. stupid user!) GroupAgent FavOrg Program: FavOrg (Bookmark Manager) GroupAgent Fetch Program: Fetch (Offline browser) GroupAgent GetRight Program: GetRight (Download Manager) GroupAgent HTTrack Program: HTTrack (Website Copier) GroupAgent Lachesis Program: Packet Loss Report (ftp.intel.com) GroupAgent lachesis Program: Packet Loss Report (ftp.intel.com) GroupAgent MSFrontPage Programming: Microsoft FrontPage (stupid user!) GroupAgent Offline Program: Offline Explorer (Offline Browser) GroupAgent Powermarks Program: Powermarks (Bookmark Manager) GroupAgent SuperBot Program: SuperBot (Web Site Copier) GroupAgent Teleport Program: Teleport Pro (Offline Browser tenmax.com) GroupAgent WebStripper Program: WebStripper (Offline Browser) GroupAgent WebZIP Program: WebZIP (Offline Browser) GroupAgent Alcatel- Device: Alcatel Mobile Phone GroupAgent AvantGo Device: AvantGo (Offline Browser) GroupAgent Blazer Device: Blazer (PalmOS browser) GroupAgent DoCoMo Device: I-mode Compatible Mobile Phone GroupAgent Elaine Device: Palm browser GroupAgent Ericsson Device: Ericsson Mobile Phone GroupAgent MOT- Device: Motorola Mobile…Read More
The leading contender for the communications protocol that facilitates the world’s business transactions is designed to transmit data over HTTP, in the clear. Although some of the creators of Simple Object Access Protocol (SOAP) have expressed concern, the consortium responsible for redrafting SOAP into the new Extensible Markup Language (XML) Protocol is nearing agreement that security is, simply put, not their problem. In the meantime — and possibly as a result– Microsoft and Verisign have just announced a new security procedure for person-to-person SOAP transactions, but a workable mechanism for securing Internet transactions between software and software may be years away. Some of SOAP’s architects contend that building security into their protocol would only sacrifice its simplicity, and that the HTTP sessions that SOAP transactions rely on can already be secured at the session level, with protocols such as SSL. Moreover, securing sessions from outside interception, security experts believe, cannot protect transactions from two other perceived threats: interception from the inside and bad programming. With a protocol extension to SOAP for message attachments in the works, a third possible threat emerges — one that too many have become familiar with: malicious scripts. Chris Dix, a SOAP programmer with FMStrategies, sides…Read More