This post originated from an RSS feed registered with .NET Buzz
by Sam Gentile.
Original Post: Occasionally Connected Computing and Your Mobile Strategy: What You Need to Know
Feed Title: Sam Gentile's Blog
Feed URL: http://samgentile.com/blog/Rss.aspx
Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More!
My boss Phil has written a excellent general piece on Occasionally Connected Computing (OCC), a new architectural approach that is emerging and one that is the centerpiece of Adesso. We consider this an evolution from previous architectural approaches although incorporating many of the (best) attributes and design patterns from the last 30 years. This approach comes with the fact that more employees in companies of all kinds and becoming mobile and that IT departments are struggling to meet their demands for information and connectivity where ever and when ever. AS Phil states, “according to IDC, there will be 105M mobile workers in 2006 and the Meta Group forecasts that 75% will be mobile 25% of the time. With these and other forecasts in mind, companies must be prepared to support “anytime, anywhere“ computing.“
Using an OCC platform, users can access data from a device (laptop, handheld, smartphone, tablet or desktop) with or without a wired or wireless connections. The key benefit is that OCC then provides a means for businesses to mobilize critical enterprise data assets by unlocking existing data and asserts and mobilizing them; allowing them to push more information to the edge of the business - where the action is.
Read the whole piece but I will summarize the features that Phil listed for OCC products that customers should consider as they are developing their mobile strategies and product support:
Provisioning for both structured and unstructured processes and content
Previous Topic
