coapp-developers team mailing list archive

[Garrett Serack <garretts@xxxxxxxxxxxxx>]

Hmmm.

Doug was one of the people in my interview loop when I got hired.

Small, small world.

Garrett Serack | Open Source Software Developer | Microsoft Corporation
I don't make the software you use; I make the software you use better on Windows.

From: coapp-developers-bounces+garretts=microsoft.com@xxxxxxxxxxxxxxxxxxx [mailto:coapp-developers-bounces+garretts=microsoft.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Justin Chase
Sent: Thursday, May 20, 2010 11:00 AM
To: Rivera, Rafael
Cc: coapp-developers@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Coapp-developers] Anyone with OData experience out there?

+1 SQL Server.

Douglas Purdy (http://www.douglaspurdy.com/) is the guy at Microsoft to talk to if you have questions. He's been on a giant OData kick lately. I have played around with it some recently and it's pretty decent, the only complaint I had was that on the client side the linq provider was pretty limited in the types of queries you could do. That's pretty reasonable still though.

You can create the OData provider quite easily by using the Entity Framework ORM tool. Which will give you everything you need to have in order to serialize / deserialize your data into objects on the server. There are hooks that you can add to filter queries using linq and add custom code for other CRUD operations. The security is pretty flexible and you can integrate it with OpenID in a fairly straight forward fashion.

So far I've been pretty impressed.

On Thu, May 20, 2010 at 11:57 AM, Rivera, Rafael <rafael@xxxxxxxxxxxxxxxxx<mailto:rafael@xxxxxxxxxxxxxxxxx>> wrote:
Using SQL Server will also allow us to port easily to SQL Azure (cloud computing) when needed.

/rafael


On 5/20/2010 12:41 PM, Roberto Carlos González Flores wrote:
+1 to SQL Server, I love the elegancy of PostgreSQL and I recognize that PostreSQL is faster than SQL Server, but we are inside a Microsoft enviroment so It would be easy to use Microsoft solutions, and C# with PostgreSQL reminds me a lot of headaches ( in my last try to put together C#/PostgreSQL ), for easy things works well, but when you trying more complex things didn't work for me.

So again, +1 to SQL Server.

--
Carlos



_______________________________________________

Mailing list: https://launchpad.net/~coapp-developers



Post to     : coapp-developers@xxxxxxxxxxxxxxxxxxx<mailto:coapp-developers@xxxxxxxxxxxxxxxxxxx>

Unsubscribe : https://launchpad.net/~coapp-developers

More help   : https://help.launchpad.net/ListHelp




_______________________________________________
Mailing list: https://launchpad.net/~coapp-developers
Post to     : coapp-developers@xxxxxxxxxxxxxxxxxxx<mailto:coapp-developers@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~coapp-developers
More help   : https://help.launchpad.net/ListHelp



--
Justin Chase
http://www.justnbusiness.com