Cross Platform Uploader and C++ Library

[Casey Link]

Hey All,

I've released the beginnings of libbitspace, a C++/Qt library for
bitspace. All it does right now is perform one upload operation at a
time.
Check it out here: http://github.com/Ramblurr/libbitspace

Also, in conjunction with the library I've released a simple uploader.
It's based on Qt, so it can be used on Windows, Mac, and Linux. It is
not quite ready for release yet, still needs some polishing.
Eventually I would like to turn it into a program to run in the
background that will automatically sync the user's music collection
with bitspace.
Check it out here: http://github.com/Ramblurr/Bitspace-Loader

Both are open sourced under GPL v3.

Best,
Casey

[Niklas Holmgren]

Great work Casey! I will try them out.

If everything seems to work well we might release the Upload API to
the public sometime next week.

We will also be releasing the Library API sometime soon. Probably at
the end of March or early April. The Library API will basically allow
anyone to build a fully functional Bitspace player, as well as other
tools and services that can benefit from having access to a users
music library. We are very exited to see what use cases you will come
up with.

Niklas

2010/3/9 Casey Link <unnamed...@gmail.com>:

[Casey Link]

Niklas,

Sounds great! Hopefully I'll have a release ready version of the
upload client soon.

I was wondering if I could get an icon from you all to use for the
uploader? My graphic design skills are non existent.

When you release the API will you make this mailing list public? That
would be helpful, because I could solicit help from users to get some
beta testers for the app. Or maybe a regular forum would be better?
Establishing an open developers community around Bitspace would, IMHO,
increase its exposure and be an all around benefit.

Regards,
Casey

[Casey Link]

Oh, I forgot to mention: I've already got some great ideas cooked up
for the Library API. So bring it on out :D

Finally, Niklas, if you'd like I can try and make some binary packages
for OS X/Windows of the upload client. I'm not sure if it will compile
out of the box on those platforms (though it should, some fiddling may
be required).

Casey

[Niklas Holmgren]

2010/3/10 Casey Link <unnamed...@gmail.com>:

> Niklas,
>
> Sounds great! Hopefully I'll have a release ready version of the
> upload client soon.
>
> I was wondering if I could get an icon from you all to use for the
> uploader? My graphic design skills are non existent.

We have put up a page about branding guidelines in the developer
documentation. There's some logos and favicons you can download there:

http://bitspace.at/developer/branding

>
> When you release the API will you make this mailing list public? That
> would be helpful, because I could solicit help from users to get some
> beta testers for the app. Or maybe a regular forum would be better?
> Establishing an open developers community around Bitspace would, IMHO,
> increase its exposure and be an all around benefit.

Yep, the mailing list will be made public together with the developer
documentation when the Upload API goes public.

>
> Regards,
> Casey
>

Niklas

[Casey Link]

Niklas,

Thanks for the branding information, I've created a simple little icon
to use for the loader.. it is attached.

I have a few questions about the Upload API:
* How exactly are sessions enforced?
* Do I need to create a new upload session for each upload? Is it bad if I do?
* Can I check to see if a session is valid?
* What does using a bad session result in?

Best,
Casey

[Niklas Holmgren]

2010/3/11 Casey Link <unnamed...@gmail.com>:

> Niklas,
>
> Thanks for the branding information, I've created a simple little icon
> to use for the loader.. it is attached.

Nice!

>
> I have a few questions about the Upload API:
> * How exactly are sessions enforced?

The upload sessions are basically a ticket that allows you to upload a
file of a certain maximum size to a certain part of an S3 bucket
withing a specific time frame. The upload will be rejected with a
standard HTTP error if the session is not valid.

> * Do I need to create a new upload session for each upload? Is it bad if I do?

You can do that if you want, but I wouldn't recommend it, as it would
probably slow things down a lot. Generating a new session each time
your app launches should be more than enough.

> * Can I check to see if a session is valid?
> * What does using a bad session result in?

You will get an error if the session is not valid, that you can either
handle automatically (recommended) or tell the user about.

>
> Best,
> Casey
>