From 8d996fa69ba99019954aaf28b5718a73d6fdbe29 Mon Sep 17 00:00:00 2001 From: halw Date: Sat, 6 Nov 2010 17:19:27 +0000 Subject: [PATCH] Added UpdateNeeded template. Class STORABLE needs to updated to SED. Assignment attempt should be object test. UNIX_ classes don't exist on Windows as stated here. Probably more issues. Author:halw Date:2010-11-06T17:19:27.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@700 abb3cda0-5349-4a8f-a601-0c33ac3a8c38 --- .../eiffelnet-tutorial/overview-eiffelnet-mechanisms.wiki | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/documentation/current/solutions/networking/eiffelnet/eiffelnet-tutorial/overview-eiffelnet-mechanisms.wiki b/documentation/current/solutions/networking/eiffelnet/eiffelnet-tutorial/overview-eiffelnet-mechanisms.wiki index ee9e2180..9978bf88 100644 --- a/documentation/current/solutions/networking/eiffelnet/eiffelnet-tutorial/overview-eiffelnet-mechanisms.wiki +++ b/documentation/current/solutions/networking/eiffelnet/eiffelnet-tutorial/overview-eiffelnet-mechanisms.wiki @@ -1,6 +1,11 @@ [[Property:title|An overview of EiffelNet Mechanisms]] [[Property:weight|2]] [[Property:uuid|08d7ca19-65e3-7f35-fbce-a50d0aedf626]] + +{{UpdateNeeded}} + + + To enable clients and servers to exchange objects, you will have to ensure that they can refer to a common '''address'''. At the predefined level this is really the only notion that you need to know, although it is useful to get the bigger picture, in particular the concept of '''socket '''(which enables systems to set up communication channels), the various forms of communication (single-machine versus multi-machine, stream versus datagram), the kinds of object structure that may be exchanged, the notion of packet, and how to associate commands with communication events. The following paragraphs review these ideas and the corresponding EiffelNet abstractions. ===Establishing a common address===