Disruptive jam. Or: more choice is not always better. I experience this on more than one domain. One actual example is GPS: I've been sniffing at various mobile GPS devices, but the choice is so overwhelming that I postpone the purchase every time again. Not that I need a GPS device so badly. I've already succeeded in memorizing the 6km ride to my job...
In Dutch, there's a saying: "To choose is to loose". So I try to win by not choosing ;-)
... finally start to make sense. I've heard a lot of buzz about them, but only now I start to understand them a bit.
One question that remains: why store "what will follow" under some key, instead of storing "what has been" under a key? Wouldn't it be easier to claim "this page id means that this user has done that and that and that, and these request parameters indicate that he will now go there". The net effect will be the same, I think, but the abstraction wouldn't leak that much (to the programmer, that is).
Let's try to restate that: instead of changing objects in a session when receiving a HTTP request, you take a copy of those objects (leaving the originals as they were), and start working on the copy. You can do the same actions that you would normally perform on the original objects. There's only one difference: the original objects are now stored in a repository under a page-specific ID. When the user has cloned her window (or pressed the back button, or...), you can fetch those objects again (thus going back to the state she was), and continue from there. In my gutt feeling, this would reduce the amount of continuation-specific code (
I think I have to re-read the article, seems like I have missed something. If you can explain me what I've missed, I will be very grateful.
Erik pointed me to NDoclet, a MSDN-style Javadoc doclet. The MSDN style seems a bit weird to somebody who's used to look things up the Sun way, but it sure looks clean. You can view the result of my little experiment here, and compare it to the more traditional approach.
Just one of those obnoxious "I'm not alone" posts.
After being a celebrity in technical circles, Steven is now moving up to the business management circles. Congrats!
Koen showed me Konfabulator. Nice looking stuff. Pleasing to the eye. And since that last item seems to be the most important nowadays (the phrase "perception is reality" comes to mind), I'm sure they'll have their share of loyal users waiting for them.
Lycos is following a weird train of thought. I thought spammers (the companies that *sell* spamming services, not the ones that buy them) would be paid by the number of clickthroughs? And I'm sure the amount of money they receive for each click is enough to cover for its bandwidth costs. Sorry, Lycos, I'm out.