zevenseas


 

How to connect your mobile device to Exchange (BPOS)

I struggled a little to get the correct settings for my Android to connect to our BPOS Exchange, follow below links to get the details:

http://www.microsoft.com/online/help/en-us/helphowto/0932dcdb-fe09-4b47-8c94-440371124341.htm

And it works.

REST and ADO.NET services

In Vegas during SPC09 I joined a session with Pablo Castro on REST and I was very very impressed! Pablo showed some samples with CURL (sorry folks, CURL indeed) and it showed how easy it is to talk to the SharePoint data services. On his blog Pablo says:

The SharePoint Data Service head is not just a side integration deal, it's a full-on REST-over-HTTP head for SharePoint. It supports browsing as well as modifying data using regular HTTP verbs (GET, PUT, DELETE, etc.), it does ETags for concurrency control, enforces business logic as part of side-effecting methods, and it handles the full range of Data Services conventions for URLs, Atom and JSON payload formats, etc. It also exposes full metadata like any other Astoria service, allowing Visual Studio and any other metadata-driven client to give you a great experience on the client side. Now if you need to get or manipulate data in SharePoint from any platform in any language, all you need is an HTTP stack.

This opens up a lot of possibilities even for PHP fans (I admit, I like unmanaged code and it is in my old set of skills). On the MSDN blogs there is a toolkit available to easy test out some REST and ADO.NET services. Till now it was almost impossible to talk to SharePoint with PHP because of the difficulties handling SOAP (you needed an external library) but that has been solved right now.

During his presentation I was also impressed with the binding of REST inside VS and that looked really great (not completely sure I got the whole picture).

The big question for the future is of course, when do you choose which interface/protocol? The SOAP services are still there and now we have REST too. And what about using the client OM, how does this all fit together?

Would be great to see some performance charts on all these different approaches in the future. My best bet is that REST will be used more and more, it is also very usable for calls from mobile devices (iPhone, WiMo and Android) and that opens up some possibilities for more vertical SharePoint apps on mobile devices (expenses, travel expenses etc.).

Two SharePoint guys that take web services really serious :-)

There are two (probably a few more) guys in the SharePoint community that do interesting stuff with SP web services, @jvossers and @sympmarc. They both work on Javascript solutions (JQuery) to make things happen inside a site(collection).

Jaap has released his LiveListData stuff and I think it is awesome. Very usable in solutions where you need to have a dashboard that shows the latest live data from updated lists, I actually think this could be something for TunnelPoint. Jaap showed it to me in Vegas and it worked very smooth.

Marc is focusing on a jQuery library for SharePoint Web Services and he tries to make it easier for (Javascript) developers to call the SP web services (correct me if I'm wrong Marc).

The solutions they provide make me think how we can use this stuff inside TunnelPoint and ProduShare, any thoughts?

New lower pricing for BPOS (significant)

Microsoft has lowered the per user price for BPOS to $10 a month (from $15). I also just saw that it can be purchased from 5 seats ongoing (thought the old model was 20 seats). The standard service also offers increased mailbox storage to 25 Gb.

Request a trial here.

The future of the web, where web sites become web services

SP2010 has been introduced and what we had in mind with TunnelPoint will be easier with SP2010. When companies will move to the cloud with SP2010 more public SP sites will become data providers, I'm convinced. If you ever heard of Web 3.0 and the semantic web did you ever realize that there is a big move towards web services and the data they provide?

I’m a big believer of an Internet of Services, where services are ubiquitous; an Internet of Things where in principle every physical object becomes an online addressable resource (see iPhone, persistent connection); a Mobile Internet where 24/7 seamless connectivity over multiple devices is the norm; and the need for semantics in order to meet the challenges presented by the dramatic increase in the scale of content and users.(source: Serviceweb 3.0 EU).

When talking about moving to the cloud the larger scope is always an Internet of Services IMO. Many companies are capable of producing very valuable information but not many companies are capable of producing very capable applications on desktops, mobiles or other devices. This is where the web services approach is at its best, companies approach developers to build applications around there data (I don’t believe in browsing on a device, sucks compared to native apps).

With the new capabilities of SP2010: client OM, REST, web services and storage of more items and data, a SharePoint portal becomes another online addressable resource. Some will say “oh Hans this will never happen because of security”, really? Start looking around and think about the new interfaces in SP2010, why does MS provide all this stuff? I think it has to do with the vision of Microsoft (see some old Bill G. essays), it really believes in an always connected world on different devices/products (desktop, mobile, tablet, surface, SharePoint). Sure, MS would like you to use al their software and devices :-) For me personally the interface is exchangeable, the data however, not!

The old perception is that closed data is a competitive advantage but the new reality is that open data is a competitive advantage (source: ReadWriteWeb). Personally I'm already a big believer for many years but SharePoint did not really offer much in terms of an active web service community or .NET developers that are looking for integration of external services into SharePoint (or I completely missed it). That has nothing to do with skills but more with focus.

For me the one part of Web 3.0 is really gaining attention and that is web services. Did you ever think about the fact that the iPhone is the perfect example of the usage of web services? A lot of the popular apps. use web services behind the scenes. Things like: traffic information, trip planning, Google Maps, LBS etc. Connected “Things” start happening too, ever heard of a service called Pachube or devices like the Chumby?

If we look at Enterprises and public SharePoint URLs, more will open up the coming years. Actually, a lot are already open because all web services related to SharePoint are enabled. Take BPOS, all is enabled out of the box.

So how does TunnelPoint fit into this story Hans? Well, we are aiming to be the connection to and from SharePoint. We do the heavy lifting and we take care of the data transformation. In SP2010 we can do more and we can do it easier because of REST (seen it and it is awesome). It is our goal to work together with developers that are believers of this approach, you can build a TunnelPoint connector too! Right now we transform data to SharePoint but one day in the future we will be capable of doing it the other way around (for example to serve your list as a KML file). Sure, this could all be done by building server side code but we want to stick to the cloud offering without the need to touch your very valuable and business critical SharePoint infrastructure.

You can find a lot of information about the Future of The web and the European Union has kicked off a huge investment in Web 3.0. For more information see the site. There is also a very interesting video here.

Another initiative is the European web service finder over here.

image


 
 
 

© 2009 Community Kit For SharePoint