Understand the semantics (and cost profile) of the AWS services first - you can't just open a HTTP connection and dribble data out over several days and hope for things to work. It is not a system that has that sort of laziness at its heart.

AWS doesn't supply a traditional remote file store semantics - is queuing, simple database and object store have all been designed for large scale systems being offered as a service to a (potentially hostile) large set of users - you can see that in the way that things are designed. There are all sorts of (sensible from their point of view) performance related limits and retries.

On 1 Nov 2011, at 06:21, dokondr wrote:

On Tue, Nov 1, 2011 at 5:03 AM, Ryan Newton <rrnewton@gmail.com> wrote:

Any example code of using hscassandra package would really help!

I'll ask my student. We may have some simple examples.

Also, I have no idea as to their quality but I was pleasantly surprised to find three different amazon related packages on Hackage (simply by searching for the word "Amazon" in the package list).

http://hackage.haskell.org/package/hS3
http://hackage.haskell.org/package/hSimpleDB

http://hackage.haskell.org/package/aws

It would be great to know if these work.

Thinking about how to implement Data.Map on top of hscassandra or any other key-value storage ...
For example creating new map with "fromList" will require to store *all* (key, value) list elements in external storage at once. How to deal with laziness in this case?

_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe