Comments on Flapjax Development Blog: Networked Persistence

Sull: Flapjax is very much meant to handle multipl...

2006-10-31T17:44:00.000-05:00

Sull: Flapjax is very much meant to handle multiple readers and writers. When you wonder whether it can, are you referring to the language or to the implementation? Perhaps this is a discussion we can carry out on the mailing list in detail?

Neel: we're very much interested in offering syste...

2006-10-31T17:42:00.000-05:00

Neel: we're very much interested in offering systematic interfaces to such services. Our Web Services interface is meant to be a bare-minimum starting point. One issue is that most of these services don't offer streaming interfaces (see my other posting on this), but we can always simulate this by polling: set up a timer behavior, convert it into an event stream, transform the event stream using the Web services call...you can figure this out. We've been watching the Amazon/Google/... data and computation space for some time now to find good fits with Flapjax.

hi. i've just stumbled here in my research on pus...

2006-10-29T01:05:00.000-05:00

hi. i've just stumbled here in my research on pushlets, http streaming etc. i've just read the primer and checked out some examples and i am excited to experiment with flapjax.
i was also going to use google web toolkit but the idea of avoiding callbacks seems more interesting to me right now so i'll first play with this.

i saw the reader/writer demo and that is more or less the basis of a new project i am beginning to sketch out. however, i am not entirely sure that flapjax can handle multiple writers/readers in its current state. like in a chat application. is this correct gathering from this post i just read?

cheers and thanks to all of you for the efforts here. very nice!

Thanks for posting this. My original comment was a...

2006-10-26T13:14:00.000-04:00

Thanks for posting this.

My original comment was actually based on a misconception -- I took the fact that you didn't have a downloadable compiler but did offer web access to it, and the fact you specified persistence to mean that you were making the availability of a particular persistent store part of the language specification.

I admit it sounds kind of dumb put like that, but powerful building-block web services (eg, Amazon's S3) have been popping up all over the place recently. So I was wondering if you were trying to figure out how to offer a systematic programmatic interface to them. They really are kind of canonical global chunks of state that are available from any computer, which is a weird new idea (at least to me).