Subject: Total Slim Down Tip

From: Flat Belly Discovery <[email-masked]>
Date: Wed, 13 Aug 2014 10:15:06 -0700

Did you hear about the DocOz discovery that targets:

- Belly Fat
- Back Fat
- Hips and Thighs
- and Flabby Arms 

All at the same time?

Its true, this shrinks all of these trouble areas without lifting a single dumbbell. 

View DocOz Episode Explanation here -> http://www.aeelsemesis.com/oz/tip/epsiode/video.shtml

[Daily Recap]

-
-
-
To stop further message notifications - write Daily Updated Alerts at 
9306 BOVA CT Louisville, KY 40291 or visit http://www.aeelsemesis.com/srki3/slft/se4h.snvkyy

-
=
-
You neglected to mention that writing a service-wrapper for a REST web service will take 100000x longer than instantly generating classes from a SOAP web service WSDL. IMO REST is good for getting a blob of data that you don't have to work with. But if you want to get an object, SOAP is way quicker and easier to implement. See my If you intend to generate a wrapper, consider using a JSON decoder instead. Let SOAP rest in peace.   Ivo It is not object oriented?. Say what?. object->xml serialize->SOAP.You're missing the point. SOAP was designed to give access to Objects as in Object Oriented Programming Objects; i.e., data plus methods. It's a terrible idea, because the set of operations that can be performed on an object locally and remotely MUST be very different; pretending latency doesn't exist when dealing with remote invocation is insane. Let it die.   Paul Sonier Jun Are you trying to say REST doesn't suffer from latency-related issues? I don't "get" your argument.   Josh M.  is
  disappointing to see this answer get so many upvotes and a bounty. It is not a helpful answer. "There is nothing useful in SOAP that can't be done with REST..". So this guy has examined every possible problem someone might have to solve and can safely say that your web service should not use SOAP (WS-* seems to be implied here)? Yeah right. I am tired of hearing strong cries of REST > WS-* or SOAP.. it is barely comparable.   Readers should note that the experience that the OP had writing a server for the first version of SOAP has little bearing on modern versions of SOAP and its related protocols.  how do you handle message level security and Reliable messaging in the rest hatting shows friendliness with Don Box. point where REST is noticeably lacking is verb usage appropriate for searching. GET seems to fit the bill most closely, however, if you want to use a complex query (eg ElasticSearch allows very complex json objects), there's not good way to send the request. Most proxies 
 have url length limits and/or don't support built one of the first SOAP web services (in 2002; Google search API). Just confirming what mdhughes says, SOAP was not a good technology. Fortunately it's past tense now and no one seriously considers using it outside of weird enterprise contexts