- From: Harry Halpin <hhalpin@w3.org>
- Date: Wed, 04 Feb 2015 19:26:44 +0100
- To: public-socialweb@w3.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/04/2015 04:40 PM, ☮ elf Pavlik ☮ wrote: > On 02/04/2015 03:37 PM, henry.story@bblfish.net wrote: >>> Maybe for our next telecon you could sketch out an alternative >>> vision, without a server-to-server protocol? >> >> yes, that is not difficult. When you say client you mean browser, >> when you mean server you mean a machine that is usually without a >> display, and that is constantly bound to the internet. In my >> world - the world of HTTP and APIs - clients and server are just >> roles that computers play. A computer program can be in server >> role in one moment and then client the next. One multiple core >> machines they can be both simultaneously. So there is no >> server/server api. There can only ever be client/server >> relations. > I just started wiki page for Social Web Glossary[1] I find it very > important to clarify terms like: > > 1 App 2 Domestic Server 3 Foreign Server 4 Web Service I in general would not use the term Web Service due to its history with SOAP, which is a separate stack. You could say simply "website" (if you mean domain, ala www.example.org running separate apps in different iframes) or just say "platform" if you mean something more cross-domain, like Twitter or Google eco-systems. Ditto domestic and foreign server. Typically, one says "provider" for domestic server and "relying party" for foreign server. There's a good terminology section here: http://www.w3.org/2005/Incubator/socialweb/wiki/FinalReport#The_Terminology > > I see scenarios where Apps (running on your local device) use HTTP > API to interact with *domestic* and *foreign* servers. Also Web > Services (running on remote servers) in some scenarios can act as > client, which can use same HTTP API as mentioned front end Apps... > > [1] https://www.w3.org/wiki/Socialwg/Social_Web_Glossary > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBAgAGBQJU0mRgAAoJEPgwUoSfMzqc5MgP/jA/nYPDZuAHBX/lGq9kfxkY RjLDXq/GnGTUjgZjZJEOYREqaRpWP1WKWZ1pvlr7eai16uMpA7USnNXdCq3ywZ3p RbNFRhkex6RA3mlDfyHWSX0+6YvjiNDbwI8v9upm+VDEW6w5scf31j4NozETK/Ff 7tEEnLp6UIy9mji343eC4vbYEO01aLA3rthjcxJxoPeK8p7cR5U5wsQfYIKElHLO JHeF0Kp0SCDRPAkvs3Mt6Eze05DwmQLLbZIeocr41l3WRMHEqdRQSSH5Qvivlzqc iXVS7GRk7sacgJfMkavVxba7R4kK6G8FzZXfOPi4S3btWL4PN1FhBXDiTG/WoV5P O9FGjaatySpqi08v9sTOXeNE1oa/ax0W9NJWuz88T2ktA4WZNeNTQlBhS/iqLeuu XX/y69E9ip/FBh5ivj8IH80Pts0/dmBBCcRmUT6bznS/lLdkp4h7ILojUHH3QYKT d9syRYYPLhAjBFyo9eH7qWnDjfEAChWN2kBfaoqFlDz3WtG8WZqh0LGkTe4SnPU8 8y2T6dRxxhHBEUlRcXXjUo6Zg19xzofOQnJhrOzud+ihCTBYTr0T39jfFYbOqF/3 Qqlk7tilcLPuG8s/+dazDtryO0DkVechuV3vrYaKbJe0cTbz08rXGIM0IoOwAfUK S0FL3ou1xMXSTIxlwGNb =OW1r -----END PGP SIGNATURE-----
Received on Wednesday, 4 February 2015 18:26:52 UTC