Hi Gregg,
On Thu, 2006-04-06 at 03:34, Gregg Wonderly wrote:
> If you are doing Java, you should be using just RMI based API interfaces to
> everything, and making using use of JERIs pluggable stack to give you the
> SOAP
> or other WS-* support you need to talk to non-Java clients/servers on the
> other
> side.
Does this imply you think of Web services as "just another distributed
object paradigm"? I think that's a dangerous assumption to make.
I think the good thing about REST is that it makes you think about the
resource, e.g. the data that you're dealing with. If Fowler's first
rule of distributed computing is "don't distribute", then the corollary
to that is to make your remote calls as coarse as possible.
The danger in approaching Web services as "just another distributed
object paradigm" is that if you approach the problem with a traditional
programming mindset using RPC interactions (local or remote), then I
would posit that you're really missing the paradigm of Web services. In
my mind, there's as big of a jump from traditional distributed computing
to Web services as there is from procedures to objects.
This isn't to say that you can't make your approach work, but I think it
isn't the best fit. A similar thing is that you can define
coarse-grained, message-based interactions via CORBA/IIOP using a MEST
style, but most people don't because that's not how they approach
problems using those technologies.
In most cases, if you don't know if the service you want is local or
remote (at least from an invocation point of view), you're likely to
make the wrong design decisions. You may choose to deploy a set of
services so that the actual communication is via in-memory messaging for
efficiency/scalability considerations, but that should not be part of
the decisions you make when you design the code that invokes it.
ast
--
Join me in Dubrovnik, Croatia on May 8-10th when I will be speaking at
InfoSeCon 2006. For more information, see www.infosecon.org.
***************************************************************************************************
The information in this email is confidential and may be legally privileged.
Access to this email by anyone other than the intended addressee is
unauthorized. If you are not the intended recipient of this message, any
review, disclosure, copying, distribution, retention, or any action taken or
omitted to be taken in reliance on it is prohibited and may be unlawful. If
you are not the intended recipient, please reply to or forward a copy of this
message to the sender and delete the message, any attachments, and any copies
thereof from your system.
***************************************************************************************************
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
