Skip to main content

Home/ OpenDocument/ Group items tagged cloud-computing

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Paul Merrell

What is Boxcryptor | Easy to use encryption for cloud storage | boxcryptor.com - 1 views

www.boxcryptor.com/boxcryptor

cloud security end-to-end-encryption

shared by Paul Merrell on 25 Mar 15 - No Cached
  • Boxcryptor is an easy-to-use encryption software optimized for the cloud. It allows the secure use of cloud storage services without sacrificing comfort. Boxcryptor supports all major cloud storage providers (such as Dropbox, Google Drive, Microsoft OneDrive, SugarSync) and supports all the clouds that use the WebDAV standard (such as Cubby, Strato HiDrive, and ownCloud). With Boxcryptor your files go protected to your cloud provider and you can enjoy peace of mind knowing that your information cannot fall into the wrong hands. Here is how it works: Boxcryptor creates a virtual drive on your computer that allows you to encrypt your files locally before uploading them to your cloud or clouds of choice. It encrypts individual files - and does not create containers. Any file dropped into an encrypted folder within the Boxcryptor drive will get automatically encrypted before it is synced to the cloud. To protect your files, Boxcryptor uses the AES-256 and RSA encryption algorithms.
  • Paul Merrell on 25 Mar 15
     
    Free for personal use. I haven't tried this yet, but the need for it has been near the top of my head since I first tried Dropbox and then realized how insecure it was. I tried a lot of sync services, but am now using Wuala, which features end-to-end encryption baked into the client software. But I also use MEGAsync for remote backup so I'[ll probably be trying this out with that service. I hope there's a way to sync the two programs.
Gary Edwards

Linux Today - OOXML/ODF: Just One Battlefield in a Much Bigger War - 0 views

www.linuxtoday.com/news_story.php3

cloud-computing grid-computing odf ooxml openxml

shared by Gary Edwards on 24 Feb 08 - Cached
  • If the OOXML format in its current form cannot get made into a true ISO standard, it could lock Microsoft out of any future plays in what could be the biggest IT revolution to date. Here are the pieces of the puzzle that fit together for me:
  • "Amazon SimpleDB is a web service for running queries on structured data in real time."
  • "Structured data." And what's a good way to contain such data? In well-built structured data file format of course. Like, for instance, the Open Document Format (ODF). And who has a vested interest in ODF? IBM certainly does. And so does Sun. And these two companies, along with Google, Microsoft, and I'm sure many others, realize that if cloud computing does indeed take off, then it will be the file format that makes the whole thing work. Which is why Microsoft feels it must get their format standardized. Even with tactics that ironically have started to attract the attention of the EU again. How else can they get a piece of the cloud pie?
  • Gary Edwards on 24 Feb 08
     
    excellent discussion of why the ISO standardization of OOXML is so importnat to Microsoft.
Gary Edwards

XML-Empowered Documents Extend SOA's Connection to People and Processes | BriefingsDire... - 0 views

briefingsdirect.blogspot.com/...red-documents-extend-soas.html

cloud-computing collaborative-computing paas saas soa woa

shared by Gary Edwards on 07 Apr 08 - Cached
  • We're going to talk about dynamic documents. That is to say, documents that have form and structure and that are things end-users are very familiar with and have been using for generations, but with a twist. That's the ability to bring content and data, on a dynamic lifecycle basis, in and out of these documents in a managed way. That’s one area.The second area is service-oriented architecture (SOA), the means to automate and reuse assets across multiple application sets and data sets in a large complex organization.We're seeing these two areas come together. Structured documents and the lifecycle around structured authoring tools come together to provide an end-point for the assets and resources managed through an SOA, but also providing a two-way street, where the information and data that comes in through end-users can be reused back in the SOA to combine with other assets for business process benefits.
  • Thus far we’ve been talking about the notion of unstructured content as a target source to SOA-based applications, but you can also think about this from the perspective of the end application itself -- the document as the endpoint, providing a framework for bringing together structured data, transactional data, relational data, as well as unstructured content, into a single document that comes to life.Let me back up and give you a little context on this. You mentioned the various documents that line workers, for example, need to utilize and consume as the basis for their jobs. Documents have unique value. Documents are portable. You can download a document locally, attach it to an email, associate it with a workflow, and share it into a team room. Documents are persistent. They exist over a period of time, and they provide very rich context. They're how you bring together disparate pieces of information into a cohesive context that people can understand.
    • Gary Edwards
      Gary Edwards on 15 Apr 08
       
      "various line of business applications and composite applications" is exactly where ODF failed in Massachusetts! Think of client/server, with many business processes bound to MSOffice on the client side. The big ODF vendors tried to convince Massachusetts to "rip out and replace" MSOffice. Which proved to be terribly disruptive and costly. These bound "client side" processes would have to be rewritten, and none of the ODF applications were the equivalent of MSOffice as a developers platform (even if the cost was something MASS was willing to pay for - which they were not!). MASS came up with an alternative idea to save ODF, the idea of cloning the OOXML plug-in for MSOffice to create an ODF plug-in. The problem was that MASS did not have an IT budget thanks to Microsoft's political mucking. So MASS CIO Louis Gutierrez turned to the big vendors askign them to support something they seriously opposed. An ODF plug-in would leave MSOffice in place.
  • ...8 more annotations...
    • Gary Edwards
      Gary Edwards on 15 Apr 08
       
      This paragraph says it all. The portable document is an essential frame for moving information thoughout the emerging client/ Web Stack /server information infrastructure model. The key is that the portable docuemnts are interactive and "live". The data and media streams bound to objects within the documents are attached to their original sources using XML connecting streams like XMLHTTPRequest or P2P Jabber XML routers. In 2003 we used Jabber to hot wire Comcast documents (docs, spreadsheet cells and presentations) to backend transactional blackboxes and web service rich data resources. The productivity gain from this approach is that end users are no longer required to verify and manage data. The "system" manages the data, freeing the end user to concentrate on the task of presentation, analysis and explanation.
    • Gary Edwards
      Gary Edwards on 15 Apr 08
       
      What? The key to client/ Web Stack /server design (advanced SOA) is to have a desktop "editor" that writes highly strucutred XML docuemnts that are universally portable across a wide range of Web Stacks. The W3C provides CDF as a very advanced docuemnt container for the purpose of porting complex documents across a wide range of "editors", servers, and devices. (X)HTML 2.0 - CSS3, SVG, XForms and RDF are the core components of the open web future where complex documents and business processes will move to client/ Web Stack /server models. The problem is that there are NO desktop "editors" capable of producing CDF. ISO approval of MS-OOXML stamps MSOffice as a standards compliant "editor". The problem is that it is very difficult to convert MS-OOXML documents to CDF - XHTML-CDF-SVG-RDF!!! The MSOffice SDK does provide an easy to implement MS-OOXML <> XAML conversion component. XAML itself is part of the proprietary WPF set of technologies, joining Silverlight, Smart Tags, and WinForms as a complete MS-Web ready alternative to advanced W3C technolgoies: XHTML, CSS, SVG, XForms, and RDF. XAML "fixed/flow" replaces XHTML-CSS. Silverlight replaces SVG and SWF (Flash). Smart Tags is a porprietary alternative to RDF-RDFa. And WinForms is of course an alternative to XForms. The MS Web STack core s comprised of Exchange, SharePoint and MS SQL Server. The core is joined by Windows Server, MS Dynamics, and MS Live (among so many). ISO approval of MS-OOXML provides the MS Cloud with a standards compliant "editor" that currently ownes OVER 95% of the desktop marketshare when it comes to bound business processes. With ISO approval, an entire generation of client/server processes can now transition to client/ Web Stack /server models, where they can take full advantage of the advanced SOA model where portable XML documents move structured data and media through a highly distributed but end user controlled web model.
    • Gary Edwards
      Gary Edwards on 15 Apr 08
       
      OK. Nice summary!
    • Gary Edwards
      Gary Edwards on 15 Apr 08
       
      Uh oh. Does Mr. Sorofman understand the importance of MSOffice-OOXML-XAML-Smart Tags as an alternative to W3C RDF? This split in the Web will result in a nightmare for Google. Think of it as though Google owns the consumer side of the web, and Microsoft owns the business process side. Such is the importance of ISO approval of MS-OOXML! Google will be unable to match the search advantages of either RDF or Smart Tags. With Smart Tagged docuemnts though, Google won't even get the chance to compete. They will be locked out of the document processing chain that begins with MSOffice-OOXML and extends through a proprietary MS Web STack rich with XAML, Silverlight, WinForms and Smart Tag semantics! Although hindsight is 20-20, we can look back at 2006 in Massachusetts and see that the failure of ODF there is going to result in huge losses to Google and Oracle. Google will find themselves locked into a consumer web box, unable to branch out to business. Oracle will find themselves on the wrong side of a Microsoft dominated client/ Web Stack /server based transition of legacy client/server systems.
    • Gary Edwards
      Gary Edwards on 15 Apr 08
       
      Great idea Mr. Sorofman, but Microsoft owns the "editor" in this equation.
    • Gary Edwards
      Gary Edwards on 15 Apr 08
       
      Another good summary statement. Convergence however is very much tied to interoperability across the emerging client/ Web-Stack /server model that represents advanced SOA, SaaS, Web 2.0 and emerging Cloud Computing models.
    • Gary Edwards
      Gary Edwards on 15 Apr 08
       
      What we found at Comcast in 2002-2003 was many spreadsheet "templates" that the sales staff used to keep track of inventory, pricing, and client accounts. By P2P enabling the cells in these templates, we were able to connect in transactional database information in real time ( or web connect time :). Every template, whether it was a writer document,-form, spreadsheet template, or presentation deck was P2P Jabber wired at the object level wherever an external information source was invloved. Which seemed to be everywhere! The hard work is getting the XML connectors in place, setting up an information stream between the Web Stack (Apache Tomcat - MySQL-XUL Server), and the backend transational black boxes. With Comcast this was done through a 24 hour dump cycle with each black box dumping and uploading from the Web Stack. For sales, marketing and management, the Web Stack did the heavy business of serving up Jabber data and resolving order conflicts. The "system" took over the management and verification of data, releasing the sales force to concentrate on their primary task.
    • Gary Edwards
      Gary Edwards on 15 Apr 08
       
      In Massachusetts, they were using eMail to shuttle spreadsheet templates around. This is about as brittle and unproductive a method as there is, but it was all they had. Rather than focusing on keeping their client side business processes operating, MASS might have been better off focusing on building a client/ Web-Stack /server model they could gradually transition these desktop bound processes to. Establish an open Web-Stack design, and work back towards the desktop client. Instead, MASS fell into the trap of trying to replace MSOffice on the desktop with ODF OpenOffice based alternatives, while simultaneously purchasing Exchange-SharePoint Web-Stack components! The MS Web-Stack is designed for MSOffice-OOXML business processes, not ODF!!!!!
  • Gary Edwards on 07 Apr 08
     
    Dana Gardner transcript of podcast interview with JustSystems and Phil Wainwright. Covers the convergence of the portable XML document model with SOA. It's about time someone out there got it. You know the portable XML document has arrived when analyst finally get it.
Gary Edwards

Is HTML in a Race to the Bottom? A Large-Scale Survey of Open Web Formats - 0 views

dsonline.computer.org/...index.jsp

cdf css html ooxml xaml xhtml

shared by Gary Edwards on 18 Apr 08 - Cached
  • The "race to the bottom" is a familiar phenomenon that occurs when multiple standards compete for acceptance. In this environment, the most lenient standard usually attracts the greatest support (acceptance, usage, and so on), leading to a competition among standards to be less stringent. This also tends to drive competing standards toward the minimum possible level of quality. One key prerequisite for a race to the bottom is an unregulated market because regulators mandate a minimum acceptable quality for standards and sanction those who don't comply.1,2 In examining current HTML standards, we've come to suspect that a race to the bottom could, in fact, be occurring because so many competing versions of HTML exist. At this time, some nine different versions of HTML (including its successor, XHTML) are supported as W3C standards, with the most up-to-date being XHTML 1.1. Although some versions are very old and lack some of the newer versions' capabilities, others are reasonably contemporaneous. In particular, HTML 4.01 and XHTML 1.0 both have "transitional" and "strict" versions. Clearly, the W3C's intent is to provide a pathway to move from HTML 4.01 to XHTML 1.1, and the transitional versions are steps on that path. It also aims to develop XHTML standards that support device independence (everything from desktops to cell phones), accessibility, and internationalization. As part of this effort, HTML 4.01's presentational elements (used to adjust the appearance of a page for older browsers that don't support style sheets) are eliminated in XHTML 1.1. Our concern is that Web site designers might decline to follow the newer versions' more stringent formatting requirements and will instead keep using transitional versions. To determine if this is likely, we surveyed the top 100,000 most popular Web sites to discover what versions of HTML are in widespread use.
    • Gary Edwards
      Gary Edwards on 18 Apr 08
       
      The summary statement glosses over the value of a highly structured portable XML document. A value that goes far beyond the strict separation of content and presentation. The portable document model is the essential means by which information is exchanged over the Web. It is the key to Web interop. Up till now, Web docuemnts have been very limited. With the advent of XHTML-2, CSS-3, SVG, XForms and CDF (Compound Document Framework for putting these pieces together), the W3C has provisioned the Web with the means of publishing and exchanging highly interactive but very complex docuemnts. The Web documents of the future will be every bit as complex as the publishing industry needs. The transition of complex and data rich desktop office suite documents to the Web has been non existent up till now. With ISO approval of MSOffice-OOXML, Microsoft is now ready to transition billions of business process rich "office" documents to the Web. This transition is accomplished by a very clever conversion component included in the MSOffice SDK. MS Developers can easily convert OOXML documents to Web ready XAML documents, adn back again, without loss of presentation fidelity, or data. No matter what the complexity! The problem here is that while MSOffice-OOXML is now an ISO/IEC International Standard, XAML "fixed/flow" is a proprietary format useful only to the IE-8 browser, the MS Web Stack (Exchange, SharePoint, MS SQL, and Windows Server), and the emerging MS Cloud. Apache, J2EE, Mozilla Firefox, Adobe and Open Source Servers in general will not be able to render these complex, business process rich, office suite documents. MSOffice-OOXML itself is far to complicated and filled with MS application-platform-vendor specific dependencies to be usefully converted to Open Web XHTML-CSS, ePUB or CDF. XAML itself is only the tip of the iceberg. The Microsoft Web Stack also implements Silverlight, Smart Tags and other WPF - .NET
  • Gary Edwards on 18 Apr 08
     
    What makes the Internet so extraordinary is the interoperability of web ready data, content, media and the incredible sprawl of web applications servicing the volumes of information. The network of networks has become the information system connecting and converging all information systems. The Web is the universal platform of access, exchange and now, collaborative computing. This survey exammines the key issue of future interoperability; Web Document Formats.
Gary Edwards

» Getting enveloped by the potential of Cloud computing | Web 2.0 Explorer | ... - 0 views

blogs.zdnet.com/web2explorer

client-server cloud-computing realestate web20

shared by Gary Edwards on 25 Jan 08 - Cached
  • By taking a fundamentally Web-based approach to the development of applications, we shift from bolting Web capabilities onto the silo toward a mode in which data and functionality are native to the Web: a mode in which the design decisions are more about modelling business requirements for limiting the ways in which data flows from one point to another rather than trying to anticipate the places in which it might be needed in order to design those pathways into software from the outset.
  • How do we change the mindset of today’s application developers, in order that they stop building ‘old’ applications in the new world?
Gary Edwards

What Cloud Means to Marketing Forecast - Nick Carr The Big Switch - 0 views

adage.com/...article

cloud-computing google grid-computing microsoft server-farms

shared by Gary Edwards on 22 Mar 08 - Cached
  • The gorilla in this nascent market is Google. It has been spending billions of dollars to build huge data centers, or "server farms," around the world, enabling it to run all sorts of consumer software and store enormous quantities of personal data. Combine that processing muscle with the company's dominance of web searching and advertising, and you have a juggernaut capable of redefining the software business on the media model.
Gary Edwards

Unbreaking the Web: IE 8 passes ACID 2 Test | John Resig - 0 views

ejohn.org/unbreaking-the-web

cdf css iso microsoft odf ooxml w3c xhtml

shared by Gary Edwards on 07 Mar 08 - Cached
  • IMHO, the key to Microsoft's OOXML strategy can be seen in the recently released MSOffice SDK. The SDK provides a component for the fluid conversion of OOXML to something called fixed/flow. The fixed part of this interesting conjunction is also known as XPS, which is designed as a proprietary alternative to PDF. The flow part is a fascinating and highly proprietary replacement for (X)HTML - CSS. Reading further through the MSOffice SDK, one can't help but be amazed at the lack of W3C technologies; especially (X)HTML, CSS, XForms and SVG. What we have instead is an entangling cascade of stuff like OOXML, fixed/flow, silverlight, XAML, and WPF. And then there is that recent promise of other high volume API's probably delivered through future Exchange, SharePoint, and MS SQL Server SDK's. So, at the end of the day, what are we looking at here? IMHO, Microsoft has figured out that the smart thing to do is leverage and extend their existing desktop monopoly into the next generation of cloud computing where the Internet platform rules. To pull this off, they have a number of problems to overcome; not the least of which is that they need to catch a break on anti trust, and, get OOXML through ISO. And oh yeah, there's that little problem that Windows can't do cloud computing.
Gary Edwards

Q&A: Nicholas Carr on the big switch to utility computing - 0 views

www.computerworld.com/...article.do

carr cloud switch utility web-platform

shared by Gary Edwards on 25 Jan 08 - Cached
  • I think we’re at the early stages of a fundamental shift in the nature of computing, which is going from something that people and businesses had to supply locally, through their own machines and their own installed software, to much more of a utility model where a lot of the computer functions we depend on are supplied from big, central stations, big central utilities over the Internet.
Gary Edwards

Has Microsoft lost its way on desktop computing? | The Apple Core | ZDNet.com - 0 views

blogs.zdnet.com/Apple

msoffice ooxml saas soa xaml

shared by Gary Edwards on 07 Apr 08 - Cached
  • OM MALIK: You outlined Microsoft’s software-plus-services strategy, but what I want to know about is the changing role of the desktop in this service’s future. RAY OZZIE: I think the real question is (that) if you were going to design an OS today, what would it look like? The OS that we’re using today is kind of in the model of a ’70s or ’80s vintage workstation. It was designed for a LAN, it’s got this great display, and a mouse, and all this stuff, but it’s not inherently designed for the Internet. The Internet is this resource in the back end that you can design things to take advantage of. You can use it to synchronize stuff, and communicate stuff amongst these devices at the edge. A student today or a web startup, they don’t actually start at the desktop. They start at the web, they start building web solutions, and immediately deploy that to a browser. So from that perspective, what programming models can I give these folks that they can extend that functionality out to the edge? In the cases where they want mobility, where they want a rich dynamic experience as a piece of their solution, how can I make it incremental for them to extend those things, as opposed to learning the desktop world from scratch?
  • Gary Edwards on 07 Apr 08
     
    ZDNet's David Morgenstern must have missed ISO approval of OOXML! MS has a desktop strategy, but involves proprietary protocols, formats and API's as the protective barrier for transitioning desktop bound client/server business processes to MS Web Stack bound SaaS-SOA business processes. Welcome to the Microsoft Cloud!
Gary Edwards

Microsoft, Google Search and the Future of the Open Web - Google Docs - 0 views

docs.google.com/Edit

webkit microsoft google search Cloud-Computing monopoly

shared by Gary Edwards on 03 Feb 09 - Cached
  • Gary Edwards on 03 Feb 09
     
    The InformationWeek series of articles outlining the challenges Microsoft faces does not cover the recent anti-trust actions by the EU - DG Competition group. Even so, the series does paint a pretty gloomy scenario. Especially if you're a Microsoft shareholder. No doubt the IW guys are shorting Microsoft. All in all, this series is an accurate assessment except for one thing; they don't credit the strength of Microsoft's monopoly position and their ability to leverage the desktop monopoly into a full fledged "business" Web monopoly. MOSS (Microsoft Office - SharePoint Server) system is kicking ass, and the world is worried that browsers like Opera are not getting a fair shake on the desktop. Microsoft is a platform player, and you can't fight that at the application level. Connecting the desktop platform to backend relational and transaction servers defines the 1995 monopoly. Connecting the desktop platform to the Web platform will define the next big monopoly play. The EU has got to get off the application layer and out of the open standards vendor consortia if they are to stop this juggernaut. The reason they need to get out of the standards consortia and write/demand their own "advanced recommendations" - like WebKit, is the cleverness of Microsoft's "duality" approach. The target has to be that of restoring competition at the high end of collaborative Web computing, where Microsoft's proprietary WPF-.NET technologies rule. Any format, protocol, or interface used to connect platforms, applications or services must be open and available to all - including the reverse engineering rights. So far the EU has left me less than hopeful. I do however believe that WebKit can get the job done. It would be nice if the EU could at the least slow the beast of Redmond down. ~ge~
  • Gary Edwards on 03 Feb 09
     
    Response to the InformationWeek article "Remaking Microsoft: Get Out of Web Search!". Covers "The Myth of Google Enterprise Search", and the refusal of Google to implement or recognize W3C Semantic Web technologies. This refusal protects Google's proprietary search and categorization algorithms, but it opens the door wide for Microsoft Office editors to totally exploit the end-user semantic interface opportunities. If Microsoft can pull this off, they will take "search" to the Enterprise and beyond into every high end discipline using MSOffice to edit Web ready documents (private and public use). Also a bit about WebKit as the most disruptive technology Microsoft has faced since the advent of the Web.
1 - 11 of 11
Showing 20▼ items per page