a tech report about Flapjax

[Shriram Krishnamurthi]

It's finally happened -- we've attempted to present Flapjax in a more
scholarly fashion! For those wondering about this, doing so was an
explicit un-goal, because papers take months to write, and that would
be time not spent writing code. But as Flapjax turns 2.5 years, we
feel the system is mature enough to warrant a first write-up. The
document is currently available as a technical report:

http://www.cs.brown.edu/research/pubs/techreports/reports/CS-09-04.html

Shriram

[Geoffrey S. Knauth]

Thanks for all your efforts! I look forward to reading the report.

[Artyom Shalkhakov]

2009/4/14 Shriram Krishnamurthi <s...@cs.brown.edu>:

I have a few questions:
- in this report, most examples use Flapjax-the-language (and not the
library). I thought that you've dropped the language, is it so?
- in section 2.8, there's a mention of "persistent objects". Where can I find
more information about them?

Last but not least, I second Geoffrey Knauth. :)

Cheers,
Artyom Shalkhakov.

[Shriram Krishnamurthi]

> - in this report, most examples use Flapjax-the-language (and not the
> library). I thought that you've dropped the language, is it so?

Ah, no! Arjun Guha put in a bravura effort to not only save
Flapjax-as-language but even improve support for it. So the language
is alive and well.

> - In section 2.8, there's a mention of "persistent objects". Where

> can I find more information about them?

Hmm...is it not in the documentation? Maybe it got dropped in the
shuffle. But either way, I suggest you ignore them for now and focus
on the Web services API, which is much more flexible. If you have a
back-end persistence server, simply expose it through the Web, and use
the WebServiceObject API instead. It'll do for most purposes.

Shriram