phracek
commented
9 years ago I think that we already have a draft of XML communication. If you don't want to add new features then you can close this issue.
More fields to protocol can be implemented later on.
Please define a draft for communication protocol which will be used between client and server.
It would be good to describe protocol here so that we can discuss about them.
The SSDS protocol should be very simple XML protocol. It will be used for communication between server and client, so it should provide information about client repo files and installed packages to the server and provide client with feedback from the server - this could be either answer to client's query or error messages describing inner server errors or dependency colving issues.
Basically the structure is very simple and it is described in protocol.txt file.
There will be two main XML tags -
will containt actual information needed by either side. Server will need information about client's system such as known repositories, installed packages, configuration files etc. Client will recieve information about packages it needs to install or error messages. Each information should have its own tag inside tag. These tags will be described in more detail in protocol.txt and will be added during development.and :will contain message code which will describe type of message. This can be used in finite automata in client or server applications to find out what kind of message was recieved. Codes will be described in more detail in protocol.txt file and will be added during development.