Server Requests

From CSSEMediaWiki
(Difference between revisions)
Jump to: navigation, search
Line 14: Line 14:
  
 
My goal here is to create a design for the application side server interface framework. HTTPS POST requests are to be used to transfer data to the server. This is just a small part of the entire app.
 
My goal here is to create a design for the application side server interface framework. HTTPS POST requests are to be used to transfer data to the server. This is just a small part of the entire app.
 +
 +
== Requirements ==
 +
 +
Strictly speaking, not too many. Mostly the good old:
 +
*something that works
 +
*is as nicely designed as practical
 +
*is as easy to understand and maintain
 +
*is flexible so that new requests can be added without much hassle

Revision as of 08:07, 28 July 2010

Filip's Design Study

Background

My design study is related to my part time job, where I am developing an application that can retrieve and plot data from a device that monitors air quality. The application is connected to a back end server where certain data is stored.

User operations that require communication with the server roughly include:

  • Requesting help (and that the user be contacted)
  • Electronically registering a device
  • Calibrating a device - data about the calibration process is uploaded

Additionally, server communication is needed when the application:

  • Authenticates with the server
  • Pings the server to ensure network connectivity

My goal here is to create a design for the application side server interface framework. HTTPS POST requests are to be used to transfer data to the server. This is just a small part of the entire app.

Requirements

Strictly speaking, not too many. Mostly the good old:

  • something that works
  • is as nicely designed as practical
  • is as easy to understand and maintain
  • is flexible so that new requests can be added without much hassle