83 REFERENCES [1] T. Van Vleck, “Electronic mail and text messaging in CTSS, 1965-1973,” Ann. Hist. Comput. IEEE, vol. 34, no. 1, pp. 4–6, 2012. [2] J. Postel, “Simple Mail Transfer Protocol”, RFC Editor, RFC0821, Aug. 1982. [3] J. K. Reynolds, “Post Office Protocol,” RFC Editor, RFC0918, Oct. 1984.. [4] M. R. Crispin, “Interactive Mail Access Protocol: Version 2,” RFC Editor, RFC1064, Jul. 1988. [5] R. T. Fielding, “Architectural styles and the design of network-based software architectures,” University of California, Irvine, 2000. [6] Google Inc., “Gmail REST API,” Google Developers. [Online]. Available: https://developers.google.com/gmail/api/. [Accessed: 08-Apr-2015]. [7] Microsoft Corporation, “Outlook Mail REST API reference.” [Online]. Available: https://msdn.microsoft.com/en-us/office/office365/api/mail-rest-operations. [Accessed: 22-Apr-2015]. [8] K. Thompson and D. M. Ritchie, UNIX Programmer’s Manual. Bell Telephone Laboratories, 1975. [9] A. Hunter, “PROFS for the Scientist,” Central Computing Division, Jan-1987. [Online]. Available: http://www.chilton- computing.org.uk/ccd/literature/ccd_newsletters/forum/p87a.htm#s1. [Accessed: 22-Apr- 2015]. [10]T. V. Vleck, “The History of Electronic Mail.” [Online]. Available: http://www.multicians.org/thvv/mail-history.html. [Accessed: 22-Apr-2015]. [11]J. van Rijn, “The ultimate mobile email statistics overview,” Email marketing consultant | Emailmonday, Jun-2015. [12] R. Gellens and J. Klensin, “Message Submission for Mail,” RFC Editor, RFC6409, Nov. 2011. [13] J. Klensin, “Simple Mail Transfer Protocol,” RFC Editor, RFC5321, Oct. 2008. [14] P. Resnick, “Internet Message Format,” RFC Editor, RFC5322, Oct. 2008. [15] J. Myers and M. Rose, “Post Office Protocol - Version 3,” RFC Editor, RFC1939, May 1996. [16] M. Crispin, “Internet Message Access Protocol - version 4rev1,” RFC Editor, RFC3501, Mar. 2003. [17]N. Borenstein and N. Freed, MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies. IETF, 1992. [18]S. Dustdar and W. Schreiner, “A Survey on Web Services Composition,” Int J Web Grid Serv, vol. 1, no. 1, pp. 1–30, Aug. 2005. [19]E. Christensen, F. Curbera, G. Meredith, and S. Weerawarana, Web services description language (WSDL) 1.1. W3C, 2001. [20]T. Bellwood, L. Clément, D. Ehnebuske, A. Hately, Y. L. Husband, and M. Hondo, “UDDI V3 Specification.” [Online]. Available: http://www.uddi.org/pubs/uddi-v3.00- published-20020719.htm. [Accessed: 22-Apr-2015]. [21]N. Mitra and Y. Lafon, “SOAP Version 1.2 Part 0: Primer (Second Edition),” W3C, W3C Recommendation, Apr. 2007. [22]K. Lawrence, C. Kaler, A. Nadalin, R. Monzillo, and P. Hallam-Baker, “Web services security: SOAP message security 1.1 (WS-security 2004),” OASIS OASIS Stand. Feb, 2006. 84 [23]A. Arsanjani, “Service-oriented modeling and architecture,” IBM Dev. Works, pp. 1–15, 2004. [24]F. Kappe, G. Pani, and F. Schnabel, “The architecture of a massively distributed hypermedia system,” Internet Res., vol. 3, no. 1, 1993. [25]R. Ekblom, “Applied Representational State Transfer", Umeå University, Department of Computing Science, 2011. [26] R. Fielding and J. Reschke, “Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content,” RFC Editor, RFC7231, Jun. 2014. [27] L. Dusseault and J. Snell, “PATCH Method for HTTP,” RFC Editor, RFC5789, Mar. 2010, 2010. [28]M. Jakl, “REST Representational State Transfer,” 2008. [29]T. Bray, J. Paoli, C. M. Sperberg-McQueen, E. Maler, and F. Yergeau, “Extensible markup language (XML),” World Wide Web Consort. Recomm. REC-Xml-19980210 Httpwww W3 OrgTR1998REC-Xml-19980210, p. 16, 1998. [30]T. Bray, The JavaScript Object Notation (JSON) Data Interchange Format. IETF, 2014. [31]A. Šimec and M. Magličić, “Comparison of JSON and XML data formats,” in CECIIS - 2014, 2014. [32]N. Nurseitov, M. Paulson, R. Reynolds, and C. Izurieta, “Comparison of JSON and XML Data Interchange Formats: A Case Study.,” Caine, vol. 2009, pp. 157–162, 2009. [33] R. Fielding and J. Reschke, “Hypertext Transfer Protocol (HTTP/1.1): Authentication,” RFC Editor, RFC7235, Jun. 2014. [34]A.Bouchez, “How to implement RESTful authentication,” 24-May-2011. [Online]. Available: http://blog.synopse.info/post/2011/05/24/How-to-implement-RESTful- authentication. [Accessed: 07-May-2015]. [35] D. Hardt, “The OAuth 2.0 Authorization Framework,” RFC Editor, RFC6749, Oct. 2012. [36]P. Prescod, “Reinventing Email using REST,” 11-Aug-2002. [Online]. Available: https://web.archive.org/web/20020811103430/http://www.prescod.net/rest/restmail/. [Accessed: 10-May-2015]. [37]L. Dusseault, HTTP Access to Email Stores. IETF, Internet Draft, 2008. Available: http://tools.ietf.org/html/draft-dusseault-httpmail-00. [Accessed: 23-Jun-2015] [38]G. Dias, D. G. . Karunarathna, G. P. D. . Udantha, J. A. I. . Gunathilake, P. S. . Pathirathna, and R. A. T. . Rathnayake, “Database based and RESTful email system with offline web based email client,” in 2011 International Conference on Advances in ICT for Emerging Regions (ICTer), 2011, pp. 127–127. [39] M. Frydrych and W. Horzelski, “DBMAIL – database architecture e mail system,” Studia Informatica, vol. 31, no. 2B, pp. 439–448, Jun. 2010. [40]M. Bazyd\lo, “RESTmail–Design and Implementation of E-Mail System as a RESTful Web Service,” Master‟s thesis, Institute of Computing Science, Poznań University of Technology (September 2009). [41]“Zimbra REST API Reference - Zimbra :: Wiki,” Zimbra: Email and collaboration for the Post-PC era. [Online]. Available: http://wiki.zimbra.com/wiki/ZCS_6.0:Zimbra_REST_API_Reference. [Accessed: 22- Apr-2015]. [42] Sendinc, “ REST API - Developer - Sendinc Email Encryption,” Sendinc Email Encryption. [Online]. Available: https://www.sendinc.com/solutions/developer/rest. [Accessed: 22-Apr-2015]. [43] Postmark, “Introduction | Postmark Developer Documentation.” [Online]. Available: http://developer.postmarkapp.com/. [Accessed: 22-Apr-2015]. 85 [44] Email Yak , Email Yak Documentation. [Online]. Available: http://docs.emailyak.com/. [Accessed: 22-Apr-2015]. [45]Context.IO, “Context.IO | lite,” Context.IO Email API. [Online]. Available: https://context.io/docs/lite. [Accessed: 22-Apr-2015]. [46]Mailgun, “API Reference - Mailgun REST API 2.0 documentation.” [Online]. Available: https://documentation.mailgun.com/api_reference.html. [Accessed: 22-Apr-2015]. [47] PostageApp, “API Overview / API / Knowledge Base - PostageApp Support.” [Online]. Available: http://help.postageapp.com/kb/api/api-overview. [Accessed: 22-Apr-2015]. [48] A. Gulbrandsen and N. Freed, “Internet Message Access Protocol (IMAP) - MOVE Extension,” RFC Editor, RFC6851, Jan. 2013. [49] P. Bryan and M. Nottingham, “JavaScript Object Notation (JSON) Patch”, RFC Editor, RFC6902, Apr. 2013. [50] M. Lanthaler, M. Sporny, and G. Kellogg, “JSON-LD 1.0,” W3C, W3C Recommendation, Jan. 2014.. [51] M. Kelly, JSON Hypertext Application Language. IETF, Internet Draft, 2013. Available: https://tools.ietf.org/html/draft-kelly-json-hal-06. [Accessed: 23-Jun-2015]. [52] M. Amundsen, “The Item and Collection Link Relations,” RFC Editor, RFC6573, Apr. 2012. [53] M. Nottingham, “Web Linking,” RFC Editor, RFC5988, Oct. 2010. [54] “PHP: IMAP - Manual.” [Online]. Available: http://php.net/manual/en/book.imap.php. [Accessed: 11-Jun-2015]. [55] C. Corbyn, Swift Mailer. 2005. [56] Open Source Initiative ,“The MIT License (MIT) | Open Source Initiative”, [Online]. Available: http://opensource.org/licenses/MIT. [Accessed: 11-Jun-2015] [57] GNU Operating System, "GNU Lesser General Public License, version 2.1",[Online]. Available: https://www.gnu.org/licenses/old-licenses/lgpl-2.1.en.html. [Accessed: 11- Jun-2015]. [58] A. L. Hors, D. Raggett, and I. Jacobs, “HTML 4.01 Specification,” W3C, W3C Recommendation, Dec. 1999. [59] E. D. Navara et.al., “HTML 5.1,” W3C, W3C Working Draft, Jun. 2014 [60] H. Steen, J. Aubourg, A. van Kesteren, and J. Song, “XMLHttpRequest Level 1,” W3C, W3C Working Draft, Jan. 2014. 86 APPENDIX A: SOURCE CODE The source code and the libraries which were used with the software have been included in the attached compact disc. A guide on how to install the software for testing has been included with the software source code.