Nick, Performance would be one major advantage for using the API directly. If you can access the API directly that would save you HTTP calls to Webdav.
Kiran -----Original Message----- From: Nick Longinow [mailto:[EMAIL PROTECTED] Sent: Monday, September 13, 2004 12:13 PM To: 'Slide Users Mailing List' Subject: RE: Using the slide api directly vs. using the webdav client Andrey That's very interesting to hear. I had been intending to do all my work with the slide api, as opposed to the webdav api. So, for creating structure ("folders", users, adding documents) I can use the server api, but for checking out and versioning documents, I will have to use the webdav api. Do you see any inherent advantage beyond this to using one api over the other ? (ie, webdav vs. server api) Nick -----Original Message----- From: Andrey Shulinsky [mailto:[EMAIL PROTECTED] Sent: Monday, September 13, 2004 2:08 PM To: 'Slide Users Mailing List' Subject: RE: Using the slide api directly vs. using the webdav client You are welcome. If you have more specific questions about slide "core" api, don't hesitate to ask. Just keep in mind that currently it is somewhat flawed - for instance, some important parts of versioning and binding mechanism are implemented in slide's "webdav" layer only. Yours sincerely, Andrey. > -----Original Message----- > From: Slide Users Mailing List [mailto:[EMAIL PROTECTED] > Sent: Monday, September 13, 2004 12:56 PM > To: [EMAIL PROTECTED] > Subject: RE: Using the slide api directly vs. using the webdav client > Importance: Low > > Thanks again, Andrey. Excellent info! > > -----Original Message----- > From: Andrey Shulinsky [mailto:[EMAIL PROTECTED] > Sent: Monday, September 13, 2004 10:45 AM > To: 'Slide Users Mailing List' > Subject: RE: Using the slide api directly vs. using the webdav client > > Hi, Nick! > > First, you should obtain an instance of the > NamespaceAccessToken class, for > example: > > Domain.accessNamespace(new SecurityToken(someObject), > namespaceName); Domain.accessNamespace(new > SecurityToken(someObject)); > > It has methods that provide you with all helpers. > > The org.apache.slide.webdav.method.PutMethod class gives some > good examples of node & descriptors creation. > > Yours sincerely, > Andrey. > > > -----Original Message----- > > From: Slide Users Mailing List > [mailto:[EMAIL PROTECTED] > > Sent: Monday, September 13, 2004 9:36 AM > > To: [EMAIL PROTECTED] > > Subject: Using the slide api directly vs. using the webdav client > > Importance: Low > > > > Hi, > > > > > > > > I am just getting started with Slide, and want to write a simple > > > > example showing how to (a) create a new file node, and (b) > > > > import a document into it, using the slide (not webdav) api. > > > > > > > > Can anyone help me with this example ? > > > > > > > > 1) Get a Strucure Helper -- getStructureHelper() -- > FROM WHERE ? > > > > 2) Create a new node in the file branch -- createObjectNode > > > > 3) Get a macro Helper - getMacroHelper() -- FROM WHERE ?? > > > > 4) Do an Import (how ??) > > > > > > > > I am trying to understand how these pieces fit together, when using > > > > the slide api (ie, what is a slidetoken, etc). > > > > > > > > Nick > > > > > > > --------------------------------------------------------------------- > 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] > > --------------------------------------------------------------------- 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] ************************************************************************ If you have received this e-mail in error, please delete it and notify the sender as soon as possible. The contents of this e-mail may be confidential and the unauthorized use, copying, or dissemination of it and any attachments to it, is prohibited. Internet communications are not secure and Hyperion does not, therefore, accept legal responsibility for the contents of this message nor for any damage caused by viruses. The views expressed here do not necessarily represent those of Hyperion. For more information about Hyperion, please visit our Web site at www.hyperion.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
