Deliver superior customer experiences with an AI-driven platform for creating and deploying cognitive chatbots
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
The content you're reading is getting on in years
This post is on the older side and its content may be out of date.
Be sure to visit our blogs homepage for our latest news, updates and information.
In past webinars & videos we’ve talked a lot about Sitefinity 4.0 being AJAXy. Without becoming embroiled in a technical conversation, this simply means that Sitefinity’s Administrative UI can respond to many of your requests without loading a brand new web page.
Instead of loading a new web page, Sitefinity only updates the part of the web page that needs changed. This results in better performance and reduces the load on the web server. Sitefinity is doing the minimum amount of work needed to respond to your request.
This gives the illusion of a self-contained client-side web application although, in reality, there are lots of micro-transactions going back & forth between the web browser and the Sitefinity web site. (If you don’t believe me, use Fiddler to watch the conversation between your web browser & Sitefinity.)
From a usability perspective all of this is a big win. This makes Sitefinity feel a lot more responsive.
As I mentioned, Sitefinity’s web services can be accessed using a traditional URL. Furthermore, Sitefinity’s web services will respond to any properly formed (and authenticated) web request. If you’re interested in testing this, create a local Sitefinity 4.0 BETA web site and access the following URL:
The service URL shown above simply returns a list of Sitefinity pages using JSON. If you don’t have any pages created, then you’ll get 0 results. Firefox & IE will download (as a file) these JSON results. Chrome, however, displays this data in the browser.
There are tons of Sitefinity 4.0 web services available for Sitefinity’s various content types. For any of these web service you can append “help” to the end of the URL to see usage instructions:
IE appears to be the only web browser that displays the help pages in an easily readable format.
Upon first glance, this may not seem very useful. However, this opens a limitless number of possibilities. Sitefinity’s Administrate UI is simply a client that accesses these web service URLs to manage the web site. This means Sitefinity’s Administrative UI is irrelevant. We don’t need it. All the real work is being done through the web services. Furthermore, if a device can hit a URL, then it can also manage a Sitefinity web site.
This means we could create new administrative interfaces for…
Each of these clients (just like Sitefinity’s official web-based UI) will make small requests to Sitefinity’s web services to fetch & manage data. Once this data is retrieved, it can be displayed in whatever format developers deem best for the device.
Creating new administrative user-interfaces is interesting, but this raw data can also be exchanged between computers. This makes it easier than ever for Sitefinity to work alongside other systems. This includes:
The reality of many CMS deployments is that the CMS sits in the midst of a diverse heterogeneous environment. These other systems may not be .NET or Windows based. Web Services, because they are utilized through URLs, are platform agnostic. This makes Sitefinity data more accessible than ever. Data can be migrated into or out of the CMS at any time.
In this blog post, I simply wanted to introduce the concepts and explore some of the advantages of Sitefinity’s web services. In future blog posts I’ll explore the technical details. In the meantime, checkout the Client-Side documentation in the Sitefinity 4.0 developer manual.
View all posts from The Progress Guys on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.