• Posts 2
  • Member Since
  • Last Active
Email
  • Birthday September 09,1959 (58 years)
  • Location: Purley, Surrey, UK
  • Occupation: C++ Developer/Consultant
All Posts Topics Started
Query on apparent mismatch between API documentation and SME Cloud Explorer method calling
I'm digging into your REST API.

There appears to be a bit of a mismatch between your published API at https://storagemadeeasy.com/?p=apidoc and SME Cloud Explorer method calling.

I attached Fiddler to the Explorer and then wrote an app to decode the API method calls it was making.

From the app, there appears to be a mismatch in the currently documented parameters for the API method [doInitUpload].

SME Cloud Explorer method call:

GET /api/14165b5c9924c8a1f04e3d3b352e5660/doInitUpload/ZnggcmF0ZSBzdG9jaGFzdGljIHZvbGF0aWxpdHkucGRm,,,ML==,ZnggcmF0ZSBzdG9jaGFzdGljIHZvbGF0aWxpdHkucGRm,eG1s,,,,Z7==,,,MjAwNC0xMi0yMCAxMjo0Njo0OT==,,,eb==,MjYzMDQw HTTP/1.1

Decoded parameters (according to the published API):

Method name: [doInitUpload]

Fewer parameters than expected for Method ( 17 vs 20 )

Parameters:

[fi_name]                      [fx rate stochastic volatility.pdf]
[fi_description]               []
[fi_tags]                      []
[fi_pid]                       [0]
[fi_filename]                  [fx rate stochastic volatility.pdf]
[responsetype]                 [xml]
[responsedata]                 []
[encryptphrase]                []
[fi_structtype]                []
[fi_id]                        [g]
[chunkifbig]                   []
[fi_localtime]                 []
[provider]                     [2004-12-20 12:46:49]
[comment]                      []
[directuploadsupport]          []
[fi_size]                      [y]
[fi_modified]                  [263040]
[metadata]                     [--- not set ---]
[fi_code]                      [--- not set ---]
[password]                     [--- not set ---]

It looks like there is an extra undocumented parameter somewhere between [fi_localtime] and [responsetype].

I suspect that the API version being used by SME Cloud Explorer is different from the online API reference.

Please can you confirm whether this is the case and e-mail me the current live API spec.


Many thanks,

John
Queries on SME API functionality

I am C/C++/C# developer with 30 years experience writing a custom document creation & editing application.

Use cases:

I want:

1) to able to upload and download document files to and from the wide range of Cloud providers, including generic Apache mod_dav WebDAV servers.

2) to be able to expose the document files via publically-accessible URLs that can be accessed natively by other users of the providers’ clouds, as well as via the application.

3) (optionally) to be able to version the file so that previous versions may also be accessible (where a particular provider supports this feature).

4) (optionally) to be able to lock files to prevent unauthorised users from overwriting or even reading those files (where a particular provider supports this feature).

 

Whilst looking for appropriate technology infrastructure to use (based on HTTP using C/C++/C#) I have gone through a path that started with REST, went through WebDAV (Lisa Dusseault’s book was most helpful), neon, serf, OpenOffice and finally arrived at SME which looks promising.

 

Questions:


Is there any SME documentation as to what settings parameters over and above (user, password) I need to supply for each Cloud provider?


In the case of WebDAV, how do I use the SME API to access a specific individual WebDAV server instance?


For WebDAV servers, what methods exist within the SME API to query/discover and specify the various Authentication schemes – Basic, Digest etc required for a particular WebDAV Server instance?


Does the SME API support methods to discover and query the Authentication schemes supported by a particular WebDAV server?


How do I programmatically determine whether a provider supports versioning and how do I specify different versions of a file to retrieve? Is this mechanism abstracted to a uniform mechanism across all providers that support versioning?

 

If I want to save a document file to a publically-exposed URL, how do I do this? How can I determine how to construct a valid URL to write to for the provider for a given user?

 

If I want to use the SME API to load from a previous specified public URL for a document, starting from the URL, how do I determine the provider’s internal folder + file name to load from the public URL provided?

 

Regards,

John

Purley, Surrey, UK

 

count post selected

Add a Website Forum to your website.