RE: Comments on SVG 1.2 from a Gecko developer

While I can think of a rare use case for having a network interface in a
local graphical editor, for p2p collaboration, that seems like a pretty
fringe case. I certainly would not expect an locally-installed SVG authoring
tool to include its own socket API.

The place where a socket API is useful is in the *viewer*, so that the user
(not the author) can communicate across the network (to get new content from
different servers, p2p communication, etc.).


MenTaLguY wrote:
| On Fri, 2004-07-09 at 15:59, David Woolley wrote:
| > > It has nothing to do with whether Java already has 
| networking APIs. 
| > > The
| > 
| > I was referring to the problem with having a network API in 
| SVG; you 
| > were refering to the problems with a particular 
| implementation of such 
| > an API.
| What I'm personally not looking forward to, as an implementor 
| of an SVG editor, is users asking me why we don't implement 
| the socket API.
| I don't think it's possible (in the context of a document in a local
| editor) to provide a sane security policy for it..
| -mental

Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (
Version: 6.0.713 / Virus Database: 469 - Release Date: 6/30/2004

Received on Sunday, 11 July 2004 16:53:32 UTC