From alex.gubashin at gmail.com Thu Nov 8 11:09:52 2012 From: alex.gubashin at gmail.com (Alex Gubashin) Date: Thu Nov 8 11:16:45 2012 Subject: [xsde-users] serialisation with periodical controlled flushing of buffers Message-ID: Hello. I'm using XSD/e for iPhone project and i have some memory allocation issues while serialising object to xml using hybrid model. It seems like serialisation part of the code consumes a way too much memory, even for small xml models. Is there any way to periodically force serializer to flush data from buffer to file? Best Regards, Alex Gubashin. From boris at codesynthesis.com Fri Nov 9 07:30:30 2012 From: boris at codesynthesis.com (Boris Kolpackov) Date: Fri Nov 9 06:55:51 2012 Subject: [xsde-users] serialisation with periodical controlled flushing of buffers In-Reply-To: References: Message-ID: Hi Alex, Alex Gubashin writes: > I'm using XSD/e for iPhone project and i have some memory allocation > issues while serialising object to xml using hybrid model. It seems > like serialisation part of the code consumes a way too much memory, > even for small xml models. Is there any way to periodically force > serializer to flush data from buffer to file? XSD/e doesn't really do any buffering during serialization. Once data is ready, it is written. I assume you use std::ostream to save the data to a file or similar. std::ofstream, for example, does some buffering. This page discuss how you can control it: http://stackoverflow.com/questions/351582/how-can-i-discover-control-the-level-of-internal-buffering-in-a-c-fstream Finally, XSD/e provides a low-level writer interface that you can use instead of std::ostream. This way you will be called every time some data is available to be written. For more information, see Section 8.1, "Document Serializer" in the C++/Serializer Getting Started Guide: Boris From alex.gubashin at gmail.com Fri Nov 9 07:04:33 2012 From: alex.gubashin at gmail.com (Alex Gubashin) Date: Fri Nov 9 07:30:42 2012 Subject: [xsde-users] serialisation with periodical controlled flushing of buffers In-Reply-To: References: Message-ID: Hi Boris, On Nov 9, 2012, at 3:30 PM, Boris Kolpackov wrote: > Hi Alex, > > Alex Gubashin writes: > >> I'm using XSD/e for iPhone project and i have some memory allocation >> issues while serialising object to xml using hybrid model. It seems >> like serialisation part of the code consumes a way too much memory, >> even for small xml models. Is there any way to periodically force >> serializer to flush data from buffer to file? > > XSD/e doesn't really do any buffering during serialization. Once data > is ready, it is written. > > I assume you use std::ostream to save the data to a file or similar. > std::ofstream, for example, does some buffering. This page discuss > how you can control it: > > http://stackoverflow.com/questions/351582/how-can-i-discover-control-the-level-of-internal-buffering-in-a-c-fstream > > Finally, XSD/e provides a low-level writer interface that you can use > instead of std::ostream. This way you will be called every time some > data is available to be written. For more information, see Section 8.1, > "Document Serializer" in the C++/Serializer Getting Started Guide: > > Boris Thanks for the answer. Best regards, Alex Gubashin From wenjiafu at foxmail.com Fri Nov 23 03:04:36 2012 From: wenjiafu at foxmail.com (=?utf-8?B?5paH5ZiJ5pan?=) Date: Fri Nov 23 03:42:18 2012 Subject: [xsde-users] =?utf-8?q?xsde-3=2E2=2E0-i686-windows_nmakefile_bug?= =?utf-8?b?77yB?= Message-ID:
Hello?
i find a bug in xsde-3.2.0-i686-windows\libxsde\xsde\nmakefile, at 586 line,there is REGEXP defined.
should is XSDE_REGEXP, is all right?
i am right or wrong?

------------------

WenJiaFu  ???

____________________

????????????????????????????????? 

NetPosa Technologies (Chongqing), Ltd.

www.netposa.com

Tel: 023-63118392 ? 6103

Mobile: +86 13594004793

EMail: wjf@netposa.com

 
From boris at codesynthesis.com Fri Nov 23 04:31:17 2012 From: boris at codesynthesis.com (Boris Kolpackov) Date: Fri Nov 23 03:52:41 2012 Subject: [xsde-users] =?utf-8?Q?xsde-3=2E2=2E0-?= =?utf-8?Q?i686-windows_nmakefile_bug=EF=BC=81?= In-Reply-To: References: Message-ID: Hi, Yes, this is a known bug that we have fixed for the next release of XSD/e: http://scm.codesynthesis.com/?p=xsde/xsde.git;a=commit;h=0ac95c0a2d6c7f8adaae4a96c2e8d8242ecd1097 It should XSDE_REGEXP instead of REGEXP. Boris