I cant say if it is better to add the extensions to wvcm or webdavclient. But I would say both should not contain any methods that are not defined in the standard.
What about adding the extensions to a special package? Than you could provide a adapter to webdavclient or wvcm.
Martin
Daniel Florey wrote:
Hi,
I'm currently working on a clusterable process engine.
To enable clustering I've added some webdav-methods that enable remote webdav-like event listening (SUBSCRIBE, UNSUBSCRIBE, NOTIFY, POLL). Have a look at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wss/wss/_esdk_arch_webdav_notifications.asp
for details.
Now my questions:
What client api is the best to access slide via webdav? I've used httpclient for get and put and am now looking into the wvcm api. As I need the remote event stuff I'd like to know if it is appreciated that I extend the api and impl to enable this feature? Or should I add this methods to the webdav-client lib and leave the wvcm untouched?
wvcm would give the advantage to hide some protocol details (NOTFIY/POLL) and give the ability to register listeners easily.
What is the right way to make some proposals for this?
It would be great if wvcm would give a complete api to access slide with all features transparently from the client side.
Regards,
Daniel
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Martin Dulisch Open Source Group, S&N AG [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
