Customer Relationship Management (CRM)
Data Farm Inc.

The Technical "Know-How"
Home Executive Summary Investors Trade Secret Compression Encryption Data Streaming Business Intelligence
Web-Mobile Services - Browser Side verse Server Side
Web pages and Mobile apps are the Enterprise Web Application View in the Model-View-Controller Design Patterns. HTML pages are static by design, but there are new and old technologies which makes these web pages dynamic. Dynamic may have several interpretation, but the goal is make web pages interactive with the user without overloading web servers with requests.

Web Pages:
JavaScript, JS, CSS, HTML5, JSP, jQuery and session control are our current tools for building these pages.

Applets and Servlets:
We had developed applets and servlets in the past and we believe applets would make Cloud Services similar to desktop swing applications. Sadly, applets are not popular in IT community. In our view Applets-Servlets communication outshine any JSP-JavaScript pages.

Browser Side verse Server Side:
As a web architect, the question of Browser Side verse Server Side is part of the architect strategies. How much coding load (calculation, error checking, processes, online help, etc) does our software client wants to move from the server to browser-side. Moving the code to the browser-side and letting site visitor's computer does the work for your application is definitely a plus. But there is nothing for free. The price or the disadvantages are developing client-side which requires scripting languages, more development time and effort plus it is a also a security issue. Not to mention the code on the browser-side must support different browsers and must work with different browser's type, Firefox, MS Explorer, Google Chrome and the list is not short.

The disadvantage of server-side processing is the page postback: it can introduce processing overhead that can decrease performance and force the user to wait for the page to be processed and recreated. Once the page is posted back to the server, the client must wait for the server to process the request and send the page back to the client.

There are many advantages to client-side scripting including faster response times, a more interactive application, and less overhead on the web server. Client-side code is ideal when the page elements need to be changed without the need to accessing the database. A good example would be to dynamically show and hide elements based on user inputs. One of the most common examples is input validation.

As for Mobile apps, we not there yet, we try to build pages that work on both web and mobile similar to our Data Farm pages.

       Facebook Facebook Facebook Facebook Facebook
Thinking in
Tiers
Data Access
Object
Interactive
Front
Zeros & Ones
Plus Math
Data and
Databases
Check List Issues
Mobile-Browsers Standardization Templates Conversion Index Performance FAQ
Cloud Intelligent JSP Template Indexing DAO-XML Security Clients
Server Personal Multiple
Languages
Encryption Tracing & Transformation Errors & Logging Future
Security &
Communication
Business Intelligent
Shopping Cart
Compression Data Structures Scalability
(Expandability)
Big Data
Business Transaction Ready to Use
DAO
  Internal &
External
Flexibility CRM
Data Refactoring Server Traffic   CLOB & BLOB Transparency End-to-End
Mapping & Farming       Encryption Availability Intelligence
Web Services       Compression Latency Marketing
New Technologies       Security Brainstorm (Team) Sales

About us Contact Site Map Support Privacy Terms All rights reserved