So if you have all 1000 in the same batch, it should essentially just be processing 1000 insert statements. While that is happening, your "commit" call is still outstanding - i.e. it has not yet received the response back. You could pretty easily add a result handler for that commit operation so your user knows when it is finished (i.e. set up a busy cursor when the commit occurs and remove it when the commit result/fault comes back).
I guess the other question is whether there is a more efficient way to insert all of those 1000 items. LC DS will add some overhead onto that process of creating those items but I would not think it would be a ton more than just the overhead of running 1000 insert statements. It would certainly be possible to create all 1000 items on the server using a remote object call, then use the DataServiceTransaction.createItem call to notify the data management system (and the flex client) that they are all there. It's not clear though that this would be more efficient. Note too that the LC DS debug logging is pretty expensive so if you turn that off, it will speed up the server a lot. Jeff From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of kcCedrics Sent: Friday, September 26, 2008 6:34 AM To: flexcoders@yahoogroups.com Subject: Re: RE[flexcoders] S: LCDS - how can I improve the createItem function? Thanks for your answer. I already did that. But the problem is the same : I have LCDS which make 1000 createItem request. In fact in my application I have my 1000 items in a datagrid, but when I check my lcds log file I see that LCDS is still creating item -- View this message in context: http://www.nabble.com/LCDS---how-can-I-improve-the-createItem-function--tp19687486p19688593.html Sent from the FlexCoders mailing list archive at Nabble.com.
<<inline: image001.jpg>>
<<inline: image002.jpg>>
