| 4 | 4 | | | 5 | 5 | The ONEsite platform is built upon the concepts of horizontal scalability and a service-oriented-architecture. We use our own web services internally to construct the web pages and features on standard social network. The ONEsite REST API provides improved response times and reliability due to load balancing and integrated support for caching. Additionally, REST improves server scalability by reducing the need to maintain communication state. This means that different servers can be used to handle initial and subsequent requests. Furthermore, as these requests are handled, less client-side software is required to be written because a single browser can access any application and any resource.Any modern programming language can utilize the data generated by the ONEsite REST API. Because all services are requested by a URL and all data is returned as XML the underlying programming language is not significant. ONEsite partners utilize Java, PHP, .NET, Python, Ruby and other programming languages to integrate with ONEsite. | | | 6 | | | | 7 | The ONEsite REST services may be accessed from a number of different locations: | | | 8 | | | | 9 | * Client Browser – i.e. a directly link to a REST RSS feed for a Blog RSS chiclet; using REST inside of a Adobe Flash file to load image thumbnails for a particular contest gallery. | | | 10 | | | | 11 | * ONEsite Platform | | | 12 | ** Modules – ONEsite modules may access the REST API and then format the resulting XML. | | | 13 | ** Pages – Pages running through the ONEsite filter may access REST for advanced functionality. | | | 14 | | | | 15 | * Third Party Sites – ONEsite partners may access the REST services to bring social network functionality and/or data into pages or services hosted externally | | 6 | 16 | |
|
