W3C home > Mailing lists > Public > www-svg@w3.org > November 2004

Re: SVG 1.2 Comment: B.2.3 Socket Connections

From: David Woolley <david@djwhome.demon.co.uk>
Date: Fri, 5 Nov 2004 07:22:04 +0000 (GMT)
Message-Id: <200411050722.iA57M5Q00779@djwhome.demon.co.uk>
To: www-svg@w3.org

> Even if you limit yourself to HTTP ports, you don't limit yourself to HTTP 
> servers.  The main use case sockets exist is for time sensitive server 
> push - stock tickers, chat, mail announcements etc.  HTTP is not appropriate 

In practice, any ordinary machine in a business environment, will only
have HTTP access and that access will only be via a proxy, so even low
level port 80 access won't work, only access through, a proxy aware,
abstract HTTP access API will work into the internet.

For many home users, you will trigger personal firewall alarms (where
I work, non-development users will also trigger them as there are now
corporate personal firewalls).
Received on Friday, 5 November 2004 07:22:08 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:14:52 UTC