Gilles Rayrat <[EMAIL PROTECTED]> writes: > Ok, so that's what I feared :) you want to re-implement a carob in erlang > The problem here is that the protocol is subject to changes... > Actually, the whole point of Carob is to insulate applications from protocol > issues.
First, as Gilles said, the protocol is likely to change, whereas API are unlikely to change (and in backward compatible way if ever). But even worst: API changes will be detected at compile time with a nice error message, whereas protocol changes will be (sometimes) detected at run-time with an obscure exception thrown. Or even a crash maybe, who knows... You have been warned :-) _______________________________________________ Carob mailing list [email protected] https://forge.continuent.org/mailman/listinfo/carob
