[EMAIL PROTECTED] wrote:
>
> Still, there's a general problem about making streaming implementations of
> DTMs be able to handle this sort of thing. I wonder if a better approach
> than just handing in the ExtendedID, is to pass in a NodeTest interface,
> and get rid of the methods that don't take a NodeTest altogether. It would
> simplify the traverser interface. Bit-o-work, though. Something to think
> about...
Is there a timeframe to get access to the NodeTest Interface ??
Changing the data model does change all the legacy implementations
and having the NodeTest is just the better solution. I would vote on
leaving the SQL interface as it is until then.
Currently streaming mode works fine as long as you don't access the
column-header information and since the column-header attributes
are replicated on each col, you can still get to that information. I would
suggest that we leave non streaming as the default but allow streaming
to be enabled. I could work up some commented examples, showing
streaming mode in operation.
JohnG
