We include managed application hosting services with all of our solutions. Our hosting approach is a blend of industry standard practices. We lease virtual private server space in a harden commercial data center from a top tier hosting provider. We then provide our clients with shared access to our private space.  While we start most new accounts with shared server allocation, once we gage overall activity and server requirements of their application, we can then move them to a different hosting configuration if needed.  The cost of this shared virtual private server hosting is included in our base rate.  The need or desire for other hosting configurations involves additional charges. For more background on information options, see Hosting Options . 

 

Server Environment - DyKIDo! uses a LAMP (Linux, Apache, MySQL, PHP) stack as its native platform. However the application can use Microsoft SQL server or PostGreSQL as alternative databases.  DyKIDo! can also run on an appropriately configured Windows IIS server with PHP 5 and PERL 5 installed.   

Our websites utilize a tiered structure that separates the user interface from the application logic and data storage.  All website content and related application data, including user session information, are stored in a SQL database. The application itself is a collection of loosely coupled independent modules that follow a MVC (model-view-controller) design framework. Most of these application modules are written using a combination of PHP and javascript.

Webpage layouts are defined in graphical templates that utilize the latest standards of HTML5 and CSS3. The separation of graphics from content allows for easily changing the look and feel of a page without requiring modifications to content. This approach is what enables the addition and modification of information without the need for a webmaster to code pages, or requirement for the authoring user to have any special knowledge.

 

Page templates interact with presentation logic through a combined use of pre-defined page positions and user access rights. Individual content items are assigned to a specific position on selected pages. (A map of typical page positions is shown below.) When a specific page is then viewed, the content from the various modules assigned to that page are presented in the assigned position, but only if the user has permission (appropriate access rights) to view that content item. If there is no content to show in a particular position, the size of the other positions automatically adjust. Multiple items can be also be set to display in each position, and adjustments are automatic. These assignments are parameter driven, which allows the layout of any page to be easily and dramatically changes by just adjusting some settings, no coding required.