Whenever something changes in the network (e.g. a new user joins, a user changes their settings on skills and interests, or a user changes location), the matching algorithm is run to compute the set of matching users. The following flowchart shows how the algorithm works. What follows is a simplified version of the actual algorithm. Further Thoughts In order to… Read more →
As already illustrated in the Architectural Design, our system follows a traditional client-server infrastructure, where the mobile application is the client that communicates with a centralised server over a REST API using JSON. The reason why we chose REST over SOAP is because REST is simple (it uses standard HTTP methods like GET, PUT, POST and DELETE), infrastructure friendly (all… Read more →
The architectural design of our RESTful application follows a traditional client-server infrastructure (see graphic below), where many clients request and receive data from a centralised server. Further information on the architectural design can be found at Standards and Protocols.