> This is an interesting topic and I didn't wanted to bring it to the scene
> until I finally take the time to write down my robustness plan for geoserver,
> but yeah, I found the parser raising a parsing thread on each call, which is
> a dangerous thing. Like it is in general a good approach f
Hi Justin,
thanks for the prompt reply.
On Wednesday 13 February 2008 07:59:06 pm Justin Deoliveira wrote:
> Wow, those results are compelling. Indeed I thought before of basing the
> streaming parser on a pull parser... seemed more natural then the hack
> of creating a separate parsing thread.
T
Wow, those results are compelling. Indeed I thought before of basing the
streaming parser on a pull parser... seemed more natural then the hack
of creating a separate parsing thread.
A 100 features taking up 606 MB seems out of hand though. Are you using
the xpath streaming method? That message
Hi Justin,
I've been working on getting the nsdi test server data rendering in udig by
using the StreamingParser in the WFS DataStore, and got it.
Yet, its leading to OOM errors on the first try. I have yet to run it inside a
profiler, though in the meantime I did a quick (simple) feature parse
