Thanks Ingo for looking into this. The byte array solution is not acceptable due to memory constraints.
I had apprehensions about available method, which you confirmed. You are right that a server side solution is the correct fix. If you have already filed a bug for this, please let me know or else I will file a bug. If someone familiar with the code could get to this before the 2.1 release, it would be very much appreciated. Regards, Ritu -----Original Message----- From: Ingo Brunberg [mailto:[EMAIL PROTECTED] Sent: Friday, July 23, 2004 7:33 PM To: [EMAIL PROTECTED] Subject: Re: Facing problem with version-controlling a resource created by Cop y method in BindingStore Forgot to say, if you need a workaround now, just read the content into a byte array and pass that to putMethod(). Regards, Ingo > Ritu, > > this needs to be fixed on the server side. > > Also your fix won't work in general because the available() method is > not reliable for computing the length. Look at its documentation. It > returns the number of bytes that can be read without blocking. That > means it will propably work for small stream sources but not for > reading from large files, for example. > > Ingo > > > Ingo, > > > > I have a client side fix for it, which I tested and it works fine. I have > > created a patch for it on the latest WebdavResource obtained from CVS Head. > > Could you please take a look at it? I am attaching it here. > > > > The fix is basically computing the length of the data from the InputStream > > by using *available* method. > > > > Regards, > > Ritu --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
