You can create test users, but for a full-blown application you are expected to take on the user management and authenticate them via OAuth. It also provides you your endpoint for your code, but doesn’t give you application users. You have a master account login that tracks your API, storage, and bandwidth. I assume this is to protect user content - even from even the vendor (a common issue/question many organizations have with cloud providers). The first thing is you can only access individual user content via the API.I finally pieced it all together and it makes more sense, but to save you some time when you’re trying yourself here are two things that you might not expect: The documentation on this is concrete, but it doesn’t exactly explain why. Another small bump I had to get over was the authentication model.It took some time to find it, but when we did the Bitcasa team fixed it within two days, which was very impressive. Getting started was a little rough for two reasons. I didn’t have time to create my own, and am also quite comfortable developing in PHP, so I decided to go with a more comprehensive Bitcasa SDK for PHP to write my application. NET SDK and it uses an old version of the API. I initially wanted the application to be a. The process is simple: upload, publish, and track. It’s very important you know what version is out in the wild. In addition to basic publishing, the app also needs to be able to manage and retract content. A real-life scenario I’ve faced several times in my industry. My goal was to create an easy-to-use publishing application that would enable you to publish individual documents to a team of field staff and external contractors. The application I used to test the API was a small content syndication web application. I have a deep background in enterprise information management and this is important because my enterprise focus, and knowing the downstream processes that file storage influences, influences my position on Bitcasa API functionality. I am a coder turned enterprise process automation specialist. I recently had a chance to spend time with the Bitcasa CloudFS APIs, but before I share more about my experience I first want to tell you a bit about my background. This is all stuff that you could write on your own, but you would be wasting your time if you did and it’s certainly not as easy as you think. It’s about creating proper versioning, management, metadata, and disposition functionality, on top of the file storage. They took what they know best about content storage, turned it into an API anyone can use, and emerged with a file system platform that can integrate into any application - whether for consumer or enterprise use.Ĭontent storage is not just about serializing files to a drive. My Experience with Bitcasa CloudFS APIsīitcasa has done something very unique: they took a consumer product and turned it into an enterprise platform. Solutions with powerful functionality that you do not need to write, and flexible enough to integrate with any application via an API.īitcasa offers just such an API. Solutions that are not only useful for business, but also as a component in modern consumer mobile and web applications. Solutions that have robust enterprise-level content features, but take the end user’s need for simplicity seriously. The modern approach is with cloud solutions and the next evolution of electronic file systems is platforms that are vigorous enough to integrate with anything. There are content management solutions built to help organizations with this problem, but they are often heavy, expensive, hard to implement and rarely adopted. And when the need arises to make that content flexible and integrate with other applications, the complexity of building one’s own cloud storage can be quite daunting. Unfortunately that assumption has led many individuals and companies down a dangerous path of poorly utilized content. Content storage seems like such a simple thing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |