Xerces-C Mini-Tech Talk: NetAccessor

[ro...@us.ibm.com]

The new NetAccessor API has already been discussed in a previous tech talk.
In 25 words or less, it allows you to plug in a handler for http:// and
ftp:// based XML entities and get them into the parser. You have to
implement the NetAccessor API and a related BinInputStream derivative, and
you can parse socket based entities.

I previously indicated that to do this, you must recompile the system and
have your per-platform code create and return the desired type of
NetAccessor when the platform independent init code asks you to. However,
since the accessor object is just stored in a public static,
XMLPlatformUtils::fgNetAccesor if memory serves, you can actually just call
XMLPlatform::Initialize(), then create your desired NetAcessor in your
code, and just point fgNetAccessor at it. At that point, the parser will
use your accesssor object.

So you can effectively just install it from your own code at run time,
using our official binary drop. This makes it a lot more flexible. You can
still of course rebuild it for your platform and have the per-platform code
create one. This will insure that the right one gets installed, without any
action on the part of the end user of the parser instance.

Note that, since the accessor object is shared within the process (its a
static member), you should be careful to provide any synchronization
required when its asked to create a new input stream. For the most part,
this won't require any synchronization, since it just requires creating a
new input stream instance over a newly created socket. So, to avoid undue
overhead, the calling code in the XMLURL class does assume it must
synchronize calls. So, if your implementation is stateful in any way, you
must provide the required synchronization.

----------------------------------------
Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
roddey@us.ibm.com

Re: next Java release?

[tw...@sauria.com]

Mark,

You should expect to see another release of Xerces soon.  The plan was
to do a release at the end of last week, and then SAX2 went and changed
all over the place, so it was decided to wait a week or so until the changes
could be made.  The current CVS version conforms to the 12/17 syntax.

Ted
----- Original Message ----- 
From: Mark Lambert <ma...@tibco.com>
To: <xe...@xml.apache.org>
Sent: Friday, February 04, 2000 5:03 PM
Subject: next Java release?


> Apologies if I've asked a common question, but I couldn't find the answer
> anywhere.  When is the next release of the Xerces Java parser coming out?
> Will it support the latest moving target coming out of the Schema WG?
> 
> markl
> 
> 
> 

next Java release?

[Mark Lambert <ma...@tibco.com>]

Apologies if I've asked a common question, but I couldn't find the answer
anywhere.  When is the next release of the Xerces Java parser coming out?
Will it support the latest moving target coming out of the Schema WG?

markl