Hi Daniel, > -----Original Message----- > From: Daniel Florey [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 17, 2004 14:27 > To: Slide Developers Mailing List > Subject: Re: wvcm questions > > > Hello again... > Some more questions: > - Why is every method in the resource interface starting with > doXXX? Isn't it > redundant as the computer is anyway doing what we want him to do :-)
Not every! ... There are also some getXXX and setXXX methods ;). Only the doXXX methods are supposed to generate traffic to the server, all other methods operate locally. There is some explanation in the javadoc of javax.wvcm.Resource: "Methods whose name begin with the prefix "do", as in "doCheckin", are redirected by the proxy to the persistent resource (all other methods operate just on the proxy itself). The state of the proxy itself is not modified by a "do" method. In particular, if the request resulted in a change to any of the property values of the persistent resource of the proxy, those changes are not reflected in the proxy, but must be obtained in a new proxy by a subsequent doReadProperties(javax.wvcm.PropertyNameList) request. The "do" methods can be expected to send and receive messages over the network to the remote server that maintains the persistent resource." > - As I've seen so far the only way to get the resource > content is to use the > method doReadContent()... This method needs an output-stream > to copy the > content to. Whould it not be much better to have a method like: > InputStream getInputStream()? The caller can now decide what > to do with this > stream (e.g. use it in a sequenceInputStream, read just the > beginning of the > stream). This is not possible with the current api. Or am I wrong? Well, the standard is still in process, there is opportunity to suggest changes. I can forward the question to the JSR-147-EG, OK? Regards, Peter --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
