Curl command line for consuming webServices?
Posting a string: curl -d “String to post” “http://www.example.com/target” Posting the contents of a file: curl -d @soap.xml “http://www.example.com/target”
Posting a string: curl -d “String to post” “http://www.example.com/target” Posting the contents of a file: curl -d @soap.xml “http://www.example.com/target”
OAauth2 framework docs : https://www.rfc-editor.org/rfc/rfc6749 (A) The client requests an access token by authenticating with the authorization server and presenting an authorization grant. (B) The authorization server authenticates the client and validates the authorization grant, and if valid, issues an access token and a refresh token. (C) The client makes a protected resource request to … Read more
Here’s my take. Although coming from a Java standpoint, I actually prefer REST. SOAP envelope with multiple namespaces and its complex structure is abomination. It tries to solve mostly imaginary problems, and doesn’t solve anything efficiently. Only thing about SOAP I’ve found useful is that it has standards for authorization and errors. On the other … Read more
The web services do allow a loosely coupled architecture. With RMI, you have to make sure that the class definitions stay in sync in all application instances, which means that you always have to deploy all of them at the same time even if only one of them is changed (not necessarily, but it is … Read more
401 Unauthorized. Your existing session token doesn’t authorize you any more, so you are unauthorized. Don’t forget that a session token is just a short-cut to avoid having to provide credentials for every request. Sending 404 is incorrect because, as you observe, the resource does exist. You just don’t currently have authorization to see it. … Read more
REST and SOAP are not equivalent concepts. REST: Depends on one transport protocol (HTTP). Makes full use of the specific features of that protocol (verbs GET, POST, PUT, DELETE, caching, headers, and predefined error codes). Says nothing about the format of the messages passed back and forth. However, since the HTTP verb and URL already … Read more
There is no standard about that, but port 8443 is sometimes known as the https-alt, and it seems the only one being popularly used as alternative HTTPS port. It may have become popular because of mod_nss (an HTTPD module alternative to mod_ssl) using it on its default configuration.
Lift’s approach to scalability is within a single machine. Scaling across machines is a larger, tougher topic. The short answer there is: Scala and Lift don’t do anything to either help or hinder horizontal scaling. As far as actors within a single machine, Lift achieves better scalability because a single instance can handle more concurrent … Read more
Let’s start by reviewing what service-discovery is – here’s a good explanation: https://www.nginx.com/blog/service-discovery-in-a-microservices-architecture/ (this link should pretty much clarify the issue asked) And here’s an example how it is used in practice: Suppose you have service B which is used by service A. Service B (like most services in SOA) is actually a cluster of … Read more
We encountered same issue and, alongside the great suggestions above, Google appears to have two complementary APIs, one for Time Zone from geocode (latitude/longitude) data and the geocode API. For example, to get the time zone and offset for San Francisco: 1) Convert the city to a geocoded location: http://maps.googleapis.com/maps/api/geocode/json?address=San%20Francisco,+CA&sensor=false The geocoded location is in … Read more