On 5 Jan 2008, at 16:52, Alexander Johannesen wrote:
> On Jan 4, 2008 8:13 AM, Gregg Wonderly <[EMAIL PROTECTED]> wrote:
>> Please, please, please go create a Javaspace application using 2 or
>> more
>> javaspaces with 2 or more lookup servers on 2 or more machines with
>> 10s of
>> producers and consumers. [...]
>> Then do the same thing with an HTTP RESTful application and report
>> back
>> here how things went. Let us know how you managed failover, resource
>> locking/unlocking, expiration of transient operations etc.
>
> Oh god, not the "as soon as you've grown up" and "once you join the
> *real* world" argument. Look, that's a cheap cop-out more than an
> argument for Jini or anything else. I'm obviously not going to create
> such a beastly system to prove or disprove that your own design is a
> good or bad one. Is it really that hard to point out why REST failed
> as opposed to, say, the developers who put the system together?
I don't see Gregg's comment as either condescending or a cop out.
The system he described would take a couple of days to put together
with commercial Jini-based products. How else are you going to learn
the costs and benefits of each approach?
Regards,
Patrick
----
[EMAIL PROTECTED]
S P Engineering, Inc.
Large scale, mission-critical, distributed OO systems design and
implementation.
(C++, Java, Common Lisp, Jini, middleware, SOA)
