Comments on: Hosting versus On-premises deployment? http://www.zimbrablog.com/blog/archives/2005/09/hosting-versus-on-premises-deployment.html All Things Zimbra Tue, 06 Jan 2009 11:38:52 +0000 http://wordpress.org/?v=2.3.3 By: http://www.01.com http://www.zimbrablog.com/blog/archives/2005/09/hosting-versus-on-premises-deployment.html#comment-23 http://www.01.com Sat, 22 Sep 2007 08:07:28 +0000 http://www.zimbrablog.com/blog/archives/2005/09/hosting-versus-on-premises-deployment.html#comment-23 List of authorized Zimbra Hosting Providers: http://www.zimbra.com/partners/zimbra_hosting.html List of authorized Zimbra Hosting Providers:

http://www.zimbra.com/partners/zimbra_hosting.html

]]> By: Hosting admin http://www.zimbrablog.com/blog/archives/2005/09/hosting-versus-on-premises-deployment.html#comment-22 Hosting admin Sat, 19 Nov 2005 02:48:41 +0000 http://www.zimbrablog.com/blog/archives/2005/09/hosting-versus-on-premises-deployment.html#comment-22 Hosted- and application-service providers can often do an even better job of providing uptime for their application or service, since it is their core expertise. I fully agree with that. Hosted- and application-service providers can often do an even better job of providing uptime for their application or service, since it is their core expertise. I fully agree with that.

]]> By: Brad Neuberg http://www.zimbrablog.com/blog/archives/2005/09/hosting-versus-on-premises-deployment.html#comment-21 Brad Neuberg Sun, 30 Oct 2005 17:25:04 +0000 http://www.zimbrablog.com/blog/archives/2005/09/hosting-versus-on-premises-deployment.html#comment-21 Hi; have you seen my AMASS framework, the AJAX MAssive Storage System? I'm trying to shift around the terms of the debate by making it possible store megabytes of information on the client-side for normal web pages; this would mean that the DHTML user interface for an application can be pushed down from a hosted service provider, but the actual data can be stored locally in the web browser for privacy reasons. See the README file at http://codinginparadise.org/projects/storage/README.html for more details. Here's a short snippet: "The AJAX MAssive Storage System (AMASS) uses a hidden flash applet to allow JavaScript AJAX applications to store an arbitrary amount of sophisticated information on the client side. This information is permanent and persistent; if a user closes their browser or navigates away from the web site, the information is still present and can be retrieved later by the web page. Information stored by web pages is private and locked to a single domain, so other web sites can not access this information. AMASS makes it possible to store an arbitrary amount of sophisticated data, way pass the 4K limit of cookies or the 64K limit of Internet Explorer's proprietary client-side storage system. An AMASS-enabled web site can store up to 100K without user permission. After 100K, users are prompted on whether the web site can store the requested amount of information. Users can approve or deny the storage request. The AMASS system informs the client-side application on whether the storage request was allowed or denied. In my own testing I have been able to store up to ten megabytes with good performance; I'm sure even more information can be stored, I just have never tried beyond this amount. AMASS works on Internet Explorer 6+ and Gecko-based browsers, like Firefox. Users must have the Flash plugin version 6+ installed to use AMASS; Flash 6+ is installed in 95% of machines, however." Hi; have you seen my AMASS framework, the AJAX MAssive Storage System? I’m trying to shift around the terms of the debate by making it possible store megabytes of information on the client-side for normal web pages; this would mean that the DHTML user interface for an application can be pushed down from a hosted service provider, but the actual data can be stored locally in the web browser for privacy reasons.

See the README file at http://codinginparadise.org/projects/storage/README.html for more details. Here’s a short snippet:

“The AJAX MAssive Storage System (AMASS) uses a hidden flash applet to allow JavaScript AJAX applications to store an arbitrary amount of sophisticated information on the client side. This information is permanent and persistent; if a user closes their browser or navigates away from the web site, the information is still present and can be retrieved later by the web page. Information stored by web pages is private and locked to a single domain, so other web sites can not access this information.

AMASS makes it possible to store an arbitrary amount of sophisticated data, way pass the 4K limit of cookies or the 64K limit of Internet Explorer’s proprietary client-side storage system. An AMASS-enabled web site can store up to 100K without user permission. After 100K, users are prompted on whether the web site can store the requested amount of information. Users can approve or deny the storage request. The AMASS system informs the client-side application on whether the storage request was allowed or denied. In my own testing I have been able to store up to ten megabytes with good performance; I’m sure even more information can be stored, I just have never tried beyond this amount.

AMASS works on Internet Explorer 6+ and Gecko-based browsers, like Firefox. Users must have the Flash plugin version 6+ installed to use AMASS; Flash 6+ is installed in 95% of machines, however.”

]]>