Version: 2008

Comments on: Forget file formats. The battle is Sharepoint

People are agog that Microsoft has announced support for Open Document Format (ODF), but I'm not sure why. This was a foregone conclusion once Microsoft figured out how to move lock-in above the file level to the content network. In other words, to Shar

Add a Comment (Log in or register) (6 Comments)
  • prev
  • 1
  • next
by kojacked May 21, 2008 11:20 PM PDT
Oh, Lord! What next? A "news" blog from someone at Symantec talking trash about McAffee's products? That's about as worthless as this tripe. Yet another blog where substituting "Microsoft" for the competition, "Alfresco", would have just as much meaning. Thanks for wasting our time Matt.
Reply to this comment
by crb0r May 22, 2008 6:30 AM PDT
I'm genuinely interested (and haven't had the time to do the research myself) - how much lock-in does Sharepoint really have? I understand the data is kept in SQL Server - is the schema public, or has it been reverse-engineered? Are the specifications published under Microsoft's new "openness initiative" of use to competitors such as Alfresco? Ignoring the implications to the GPL for a second, could Alfresco buy a patent license, and offer a version that connected to Sharepoint using these protocols, or even better, implement a connector using the specs without violating any of Microsoft's patents?
Reply to this comment
by weharc May 23, 2008 2:43 PM PDT
I'd like to know what Matt thinks is lock in. SharePoint has several options for getting content out: 1) Use the web services that are provided out of the box. 2) Use the object model API and write three lines of code to get the file out (see http://blah.winsmarts.com/2008-5-CNET_-_please_do_your_research_before_opening_your_big_mouth.aspx)
3) Create a linked table with Access (no code solution, might be more applicable to List based data than binary attachments). So based on this, this whole post looks like typical FUD from someone who doesn't know what they are talking about.
by hassanibraheem May 23, 2008 9:26 AM PDT
This deserves some research.
Please fix the lwn.net and infoworld.com links.
Reply to this comment
by aravindlive May 29, 2008 3:35 AM PDT
Documents stored inside SharePoint can be recovered / retrieved by using Sharepoint object model.

1. Refer the Sharepoint object model library in a project ,
2. Write a console application and replace siteURL string with your SharePoint site url
3. At the end of execution of third line you will get the document at byte array

SPWeb web = new SPSite(siteURL).OpenWeb();
SPDocumentLibrary dox = web.Lists["Documents"] as SPDocumentLibrary;
byte[] fileBytes = dox.Items[0].File.OpenBinary();

Above lines may be too technical for a user but it's really an easy job to recover.
Reply to this comment
by jalvarado77 June 9, 2008 7:59 PM PDT
Matt, you are full of garbage! Please take a class in Sharepoint and learn it before you make such ignorant remarks. Come on, you are loosing credibility here.
Reply to this comment
(6 Comments)
  • prev
  • 1
  • next
advertisement

15 sites that went kaput in 2009

Web sites launch all the time, but they also shut their doors. We highlight 15 that bit the dust this year.

Top 10 news stories of the decade

Let the debate begin: Was the iPhone more important than iTunes? Was anything bigger than Google finding a great business model? CNET offers its list of the 10 most important stories of the '00s.

About The Open Road

Matt Asay brings a decade of in-the-trenches open-source business and legal experience to the Open Road, with an emphasis on emerging open-source business strategies and opportunities. Matt is general manager of the Americas division and vice president of business development at Alfresco, a company that develops open-source software for content management. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure.

Add this feed to your online news reader

The Open Road topics

advertisement
advertisement