Hi,
Are you talking about a public free cloud? Nobody needs to offer that, as I
say, any desktop can work as it's own server, so anyone can install it
locally, having a little cloud installed in their own desktop. And if, a
company wants to offer it on a server for many people, it will work too.
Do you understand what I mean? Any vendor could provide a SaaS solution too.
Look at Zimbra (PIM), for example, they have a full functional web
interface.
Enterprises are looking to reduce TCO with public or private clouds, so that
they don't have to manage and administer clients.
Cheers!
On Thu, Jan 27, 2011 at 22:39, Andy Brown <andy@the-martin-byrd.net> wrote:
On Thu Jan 27 2011 13:32:42 GMT-0800 (PST) Jaime R. Garza wrote:
Exactly, that's my point, having a HTML5 GUI, you can install it locally
or
in the cloud. You can always install it in a desktop for offline usage.
And just who is going to put up the money to pay for this "cloud"? I, for
one, do not have several thousand dollars(US) to pay for such.
--
Unsubscribe instructions: E-mail to
discuss+help@documentfoundation.org<discuss%2Bhelp@documentfoundation.org>
Archive: http://listarchives.documentfoundation.org/www/discuss/
*** All posts to this list are publicly archived for eternity ***
--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Archive: http://listarchives.documentfoundation.org/www/discuss/
*** All posts to this list are publicly archived for eternity ***
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.