shaxs:1) With Amazon S3 you are allowed 99 buckets. I think I read that Nirvanix uses folders. I think I also read that they were unlimited. So, if we are building an application that requires us to track exactly how much file space a specific account is using, we could have a separate folder for each account and calculate how much space is in that folder?
We have the concept of folders but we also allow child accounts. A child account is a unique file space within an application that can have limits placed for the storage and bandwidth. You can also get current usage for a child account programmatically and through our management portal.
shaxs:2) Do you guys have cname aliasing for storage could service? Meaning instead of Nirvanix’s name in the url when pulling assets, could we have our own domain instead?
We refer to these as Virtural URL's which can be setup as CNames or you can delegate a sub-domain to use to have us manage that for you. Once it is setup you would refer to your files as http://services.yourdomain.com/ or http://nodeX.yourdomain.com/. If you delegate a subdomain it would be services.subdomain.yourdomain.com. Also this feature allows you to map to a specific application or child account meaning you can hide which account / application you are accessing such as:
http://services.nirvanix.com/yourapp/yourchild/yourpath/file.txt
could be:
http://services.yourdomain.com/yourpath/file.txt or http://services.yourdomain.com/yourchild/yourpath/file.txt
shaxs:3) We have been trying to get either SWFUpload or Fancy Upload to work with Amazon S3 to no avail. From what I understand, this is due to the type of method Amazon requires to send files from a browser. Nirvanix supports standard HTTP post which means either one of these javascript / flash uploaders should work correctly?
We have a flash upload in the download section you can take alook at if you are doing your own. We also have had a number of external uploads used with customers products successfully. A standard post will work as long as you can get the upload token and append to the URL before uploading. We have a two step process that you request the node and security token which is then used to tell the uploader where to upload and how to authenticate.
We haven't specifically tested either of those but I don't see a specific reason why they wouldn't work. If you have tried them please let us know if they work or if they don't, we have made changes in the past that allow 3rd party uploaders work correctly.
Regards,
Barry R.