EMU/Protocol: Difference between revisions
Jump to navigation
Jump to search
m →Client |
m →Client |
||
| Line 3: | Line 3: | ||
====Client==== | ====Client==== | ||
login | * login | ||
version | version | ||
projectname | projectname | ||
| Line 9: | Line 9: | ||
password | password | ||
update_request | * update_request | ||
wants to receive new files | wants to receive new files | ||
unlock_request | * unlock_request | ||
wants to edit a code chunk | wants to edit a code chunk | ||
upload_chunk | * upload_chunk | ||
upload an edited chunk | upload an edited chunk | ||
relock_request | * relock_request | ||
wants to end locking session | wants to end locking session | ||
lock_status_request | * lock_status_request | ||
get information about all classes | get information about all classes | ||
online_status_request | * online_status_request | ||
get information about online users | get information about online users | ||
logout | * logout | ||
informs about a logout of the client | informs about a logout of the client | ||
Revision as of 17:37, 17 May 2006
Messages
Messages are encapsulated within objects that are being transmitted over the network.
Client
- login
version projectname username password
- update_request
wants to receive new files
- unlock_request
wants to edit a code chunk
- upload_chunk
upload an edited chunk
- relock_request
wants to end locking session
- lock_status_request
get information about all classes
- online_status_request
get information about online users
- logout
informs about a logout of the client
Server
login_accepted
login_denied
update class files
unlock_request_granted checks status sets status
unlock_request_denied status information
lock_status send status information of all classes
online_status send status of users online
server_down send information about server down
send_message send a message to all clients