A Java Project
Client must have a GUI. Minimal GUI requirements are:
• Text field to provide IP address of the server
• Text field to provide port number
• Connect/Disconnect button
• Text area to type in text to be sent to server and POST button
• GET button with dialogue to enter required properties
• PIN, UNPIN buttons with a dialogue to supply coordinates
• CLEAR, SHAKE buttons
• Text area to display result of the request.
and
Clients will:
• Request a connection with the server
• Send different types of messages through established connection:
1. POST <note>
2. GET <request>
3. PIN/UNPIN <data>
4. CLEAR/SHAKE
5. DISCONNECT
defines
<data> is a pair of integers, describing x and y coordinates of a point on the board.
<note> is similar to post-it note (colored rectangular piece of paper containing a string): it is completely
defined by the coordinates of lower-left corner, width, height, color, message and status
(pinned/unpinned). To POST a note, client must completely define it. For example:
POST 2 3 10 20 white Meeting next Wednesday from 2 to 3
POST 6 6 5 5 red Pickup Fred from home at 5
When notes are originally posted, they are not pinned. To change the status a client can used PIN or
UNPIN command. For example,
PIN 4,4
will pin all notes that contain the given “pin coordinates”. In the example above the first note will be
pinned, while
PIN 7,7
will change the status of both notes to pinned. The meaning of UNPIN is obvious. However, remember
that a note can be pinned by more than one pin. So, UNPIN command does not necessary changes the
status of a note.
<request> field in GET command has two forms. The first one is
GET PINS
which forces the server to “supply” a client with coordinates of all pins.
All other requests have the following general form:
color=<color> contains=<data> referesTo=<string>
For example
GET color=white
will force the server to “supply” a client with all “white” notes on the board.
GET contains= 4 6
will force the server to supply a client with all notes that contain point with coordinates (4,6).
GET contains= 4 6 refersTo=Fred
will force the server to supply a client with all notes that contain point with coordinates (4,6) and have
substring “Fred” in the content.
Generally,
GET color=<color> contains=<data> referesTo=<string>
will force the server to supply client with information of all notes of the particular color that contain
given by <data> point and have substring <string> in the content. If one of criterions is missing – the
semantics of request is ALL (for example, no color in GET means ALL colors)
