team15-design

A native user interface offers advantages to both

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: ffiliation with the institution simplifies the problem of identity management for both developers and users. Board structure Options 1. Flat 2. Arbitrarily nested 3. Specific depth Decision: Arbitrarily nested This was the model used by the defunct newsgroups which provided the inspiration for Unity. This model is also familiar from other environments such as mailing lists. However, this need not dictate the UI presentation. Messaging protocol Options 1. 2. 3. 4. NNTP IMAP XMPP HTTP/REST/JSON Decision: HTTP/REST/JSON We considered using an existing messaging protocol but found them to be complex and lacking in client library support. Notification protocol Options 1. Client polling 2. MQTT 3. C2DM Decision: C2DM A push model is favored to reduce network utilization and client device battery drain. MQTT is cross-platform but would require a Unity administrator (and the developers) to operate an MQTT broker. C2DM is specific to Android but uses Google's servers. The notification subsystem will be sufficiently abstract to allow future use of other services, such as Apple's APNs. 6 Server Implementation language Options 1. 2. 3. 4. Java C# Python PHP Decision: Pytho...
View Full Document

Ask a homework question - tutors are online