SCO Forum 2004 to unveil latest product strategy

News

SCO Forum 2004 to unveil latest product strategy

As customers and resellers gather for the annual SCO Forum in Los Angeles most will probably be wondering about how the group's strategy will be affected by its Linux code infringement lawsuits against IBM, Novell, and others.

SCO is expected to announce some upcoming products, including the first developer's preview of SCO's next OpenServer release, codenamed Legend.

The Legend project was unveiled at last year's SCO Forum, and is expected to ship in the first quarter of 2005.

Legend will increase the number of applications available to SCO OpenServer customers and will include a new developer environment to create a single application for use in OpenServer and UnixWare environments.

It is also expected to include increased performance and scalability for symmetric multiprocessing and load-balancing requirements.

Chief executive Darl McBride opened Monday's sessions with a presentation about "SCO Past, Present and Future", while Erik Hughes, director of product management, is expected to outline SCO's product road map.

SCO will also announce the availability of the latest version of SCOoffice Server 4.1, to provide an e-mail and collaboration server product for small- to medium-sized businesses as an alternative to Microsoft's Exchange Server 2003, and the SCO Marketplace Initiative, which is a new feature of the SCO Developer Network.

Customers seeking custom development work for their SCO Unix projects would be able to seek bids from developers using an online bidding process by the end of the year.

Todd R Weiss writes for Computerworld
 
 
 

 


Email Alerts

Register now to receive ComputerWeekly.com IT-related news, guides and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
 

COMMENTS powered by Disqus  //  Commenting policy