John Morrison wrote:
> > Agreed. -1 as well. Well, until somebody comes up with the need for an
> > action to be executed *after* a serializer.
>
> How about this one: if the serializer doesn't throw an exception then
> you *know(?)* the client recieved the request. An action after
> serialization maybe to log the fact that they got it perhap for usage
> charging...?
Clever example, but the question mark you used is the key: there is no
way to tell if the fact that serialization was complete automatically
implies that the browser really received that data.
User complains will force you to turn it into a subscription-based
format, where validation (and payment) is performed *before* the page is
viewed.
Also, micropayments will never work no matter what technology powers its
security because the amount of 'frustration' intrinsic the act of
'buying' (measuring the relefance of a choice) is not linearly
proportional with the amount of money exchanged. For example. flat rates
are percieved as less expensive, because they reduce the amount of
frustration at one big choice instead of a miriad of small ones.
Anyway, since exceptions can be logged, it would be pretty easy to
post-process the logs for charging even without the need for a specific
action.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
