I'm stealing this directly from the ADO.NET Data Services documentation here: http://msdn.micro... However, it's all in a Word document (??) right now, so I thought I'd repost to something that might be a bit easier to find. Structure of Web Data Services URLs The basic format for URLs is: http://host/vdir/... Note: in the syntax above [ ] imply optional components The 4 main elements of the URL syntax are: 1. The data service URL. The ...

Thanks to all that came out. I appreciate you taking a listen. I've uploaded the Sql Cache Dependency Patterns presentation notes and demos for you all to enjoy. Also, below is the copy from the handout that was available at the meeting (also in the zip file for download). Summary of SQL Server 2005 Cache Dependency Patterns Declarative SqlDependency Overview Declaratively add database dependencies into your ASP.NET web applications using an attribute-based approach. Dependencies can ...

So check this out. I'm prepping for this presentation and I'm planning on boring my audience with yet another AdventureWorks sample DB demo. In case you haven't noticed, they've recently moved all Microsoft SQL Server sample DBs to CodePlex. Anywho, I was trying to download the sample DB from CodePlex and it was taking forever. So I used this spare time to write on Twitter about it. Nothing horrible, just sort of a prayer to ...

Update: Subject changed. I'll be speaking on SQL Server Cache Dependency Patterns I'll be speaking on Distributed Caching with Microsoft Velocity at the August 20th CNUG meeting. Meeting is at the Downers Grove Microsoft office.

I thought it would be good to put up the physical and logical models of Velocity so you can all get a grasp of what it looks like. Physical Topology Below is the physical topology of a Velocity caching tier. As you can see, each cache cluster contains one or more cache servers (hosts) with an instance of Velocity running on it as a Windows service. The individual hosts are each cognizant of a folder ...

Something that I think a lot of software developers have dealt with when building high availability web applications is how to manage distributed cache. It's one thing to be able to get your data/objects into cache, but it's another thing to come up with a great cache synchronization architecture that's reliable and scalable. To break down the common synchronization problem simply: In a load balanced environment, how do changes made on one server, force cache ...

I had been hearing quite a bit about the David Heinemeier Hansson speech at Startup School, and finally got around to watching it. It's a pretty smart presentation. Have a look.