[xsd-users] Partial update of in-memory structures & network transfer.

[Moss, David R (SELEX Comms) (UK Christchurch)]

Boris,

> Would you like a pre-release binary?
Yes, that would be great.

> Maybe we should think about a mechanism that would allow generic 
> navigation/modification of the tree (higher-level than DOM but
lower-lever 
> than static typing).
Priorities have shifted a bit here so my thoughts on this maybe a bit
intermittent! I was thinking about somehow extracting the schema path of
the fragment (along with ids for sequence resolution) and passing that
to access the area of data to be changed:

car_t master ...;
car_t fragment ...;

database<car_t> db;

db.query( 	master, 		// object to update
		fragment, 		// the 'request'
		fragment.path(), 	// e.g.
<root/car/wheel/pressure/>
		fragment.keys(), 	// collection of xsd:any to
resolve sequences 						e.g.
wheel id.
		"replace" 		// replace, insert, remove.
	   );

Not sure how to indicate the update mode. Not sure about any of it to be
honest!


Cheers,
Dave

Dave Moss
SELEX Communications
Grange Road
Christchurch 
Dorset  BH23 4JE
United Kingdom
Tel: + 44 (0) 1202 404841
Email: david.r.moss at selex-comm.com


> -----Original Message-----
> From: Boris Kolpackov [mailto:boris at codesynthesis.com]
> Sent: 24 May 2006 13:54
> To: Moss, David R (SELEX Comms) (UK Christchurch)
> Cc: xsd-users at codesynthesis.com
> Subject: Re: [xsd-users] Partial update of in-memory structures &
network
> transfer.
> 
> Hi David,
> 
> Moss, David R (SELEX Comms) (UK Christchurch) <david.r.moss at selex-
> comm.com> writes:
> 
> > > car_t car = ...
> > > ACE_OuputCDR ocdr;
> > >
> > > ocdr << car;
> > >
> > > // One can extract binary representation of car from ocdr now.
> > >
> > > ACE_InputCDR icdr (ocdr);
> > > car_t car_copy (icdr);
> > >
> >
> > This definitely sounds like something we could try out if it's not
> > diverting you from your planned development :-)
> 
> I have ACE CDR stream insertion and extraction implemented for non-
> polymorphic case. Testing it on a 1051 bytes XML file (library.xml)
> resulted in 351 bytes of binary representation. For comparison, zip-
> compressing the same file resulted in 595 bytes.
> 
> Would you like a pre-release binary?
> 
> hth,
> -boris