Geeks With Blogs
Gizmox - Guy Peled's Blog Guy Peled's thoughts on development, and what ever...

The following post is taken from an article that explore the differences, pros, cons and usages scenarios of the Server empowered web architecture of Visual WebGui and on the other side the Client empowered web architecture features by solutions such as Classic AJAX, Flex/Flash, Classic Silverlight, Java Applets.

Both server and client empowered solutions can support any kind of UI look & feel using Silverlight or rich AJAX.

Client empowered applications support the highest performance in applications that data interactions are less common than pure UI/animations/media interactions.

Gaming, animations, and, most of the editors are not security critical applications so that client solutions are valid for those, however, server empowered solutions and more specifically Visual WebGui is much more secured by design.

Client footprint is the parameter representing the download weight as a function of the application’s complexity. When client UI interactions, animations, and media are more common, and the software updates frequency is relatively low, then client solutions tend to be more efficient regardless their weight. However, in any other case the small & static footprint of Visual WebGui server empowered paradigm is much more efficient and reasonable.

Client empowered solutions are virtually more scalable as they reduce mass responsibilities from the server. However, when the intensiveness of data interactions is higher than UI changes or heavy animations and media, Visual WebGui server empowered paradigm provides the best scalable and redundant solution.

ull virtualization of the desktop environment i.e. Registry and File system is enabled within Visual WebGui server as a complementary service, providing full virtualization of desktop environment for web/cloud applications.

Media, streaming and animations based applications, require the flexibility of Silverlight and Flash client based applications, the set of tools offered in this family of development tools is more graphic designer oriented and adapted. Visual WebGui server empowered paradigm with single layered object oriented code, desktop like form designer, point & click customization, and data designed set of controls, developer gains great advantage when developing data/business centric application. It simplifies and cuts about 90% of this kind of apps development time.

Maintaining single layered object oriented code is preferable in all cases than any kind of multiple layers and technologies. Even Silverlight which enables Dot.Net in the client requires the establishment of application .NET client & XAML infrastructures and .NET server code as data infrastructures in different layers.

The same tools are available for web UI (DHTML/Silverlight) customization whether the architecture is client empowered or server empowered. However, customizing data controls and business functional UI is enhanced and boosted with the Visual WebGui server empowered paradigm point & click controls designer.

Sharing WPF/Silverlight XAMLs, code & resources may result in some level of presentation freedom (enabling the use of the same application from multiple devices and media). Though, the complete decoupling of Visual WebGui server empowered paradigm code from the presentation layer provides full capabilities to choose any device as an alternative presentation layer (plain browsers, Silverlight, Flash, mobile devices, smart clients etc).

You can read the original article here...

Posted on Thursday, July 16, 2009 4:28 AM Design Patterns , Frameworks , Visual WebGui , Web | Back to top


Comments on this post: Server vs. Client Empowered Web Applications

No comments posted yet.
Your comment:
 (will show your gravatar)


Copyright © Guy Peled | Powered by: GeeksWithBlogs.net