2011/3/26 Cédric Beust ♔ <[email protected]> > > > On Fri, Mar 25, 2011 at 9:20 PM, mP <[email protected]> wrote: >> >> >> I smell a remote ejb stub :) In practical terms end developers never try >> any of these simply because the API does not present an opportunity to retry >> on a different cluster node simply because they are not aware of the >> available nodes. When working w/ remote services throwing RE becomes another >> problem that can happen at any time like OOME >> > > I don't think the comparison to OOME is justified, because > > - OOME can literally happen at any time. Really, any time. > - When OOME happens, there is very little left to do but crash. > - RemoteExceptions can only happen when you call a remote method. > - As I showed above, you can do something meaningful when a > RemoteException occurs. > > > Hey, why not just "let it crash" for everything? It certainly works for Erlang, where *everything* is a remote call to another process. It's been used very successfully in telecoms switches with over 2 million lines of code and nine-nines reliability; a few nanoseconds of downtime annually.
And no, it doesn't have checked exceptions (though it does have the regular variety) > and for the sake of simplicity it probably makes sense to group it as >> such. A lot of Springy ppl and users seem to think this way and its got a >> lot going for it. >> > > By "a lot", did you mean hundreds of lines of meaningless stack traces in > logs? > > Yes, I certainly agree with that :-) > > -- > Cédric > > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- Kevin Wright gtalk / msn : [email protected] <[email protected]>mail: [email protected] vibe / skype: kev.lee.wright quora: http://www.quora.com/Kevin-Wright twitter: @thecoda "My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger" ~ Dijkstra -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
