﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Ayende Rahien commented on Who let that smart client into my database?</title><description>That is something else all together, of course, which doesn't have the same set of constraints as server/client apps
</description><link>http://ayende.com/2320/who-let-that-smart-client-into-my-database#comment7</link><guid>http://ayende.com/2320/who-let-that-smart-client-into-my-database#comment7</guid><pubDate>Thu, 19 Apr 2007 19:33:40 GMT</pubDate></item><item><title>Harald commented on Who let that smart client into my database?</title><description>what about apps with a local or even in-memory database, you obviously won't want to have a webservice in between :)
</description><link>http://ayende.com/2320/who-let-that-smart-client-into-my-database#comment6</link><guid>http://ayende.com/2320/who-let-that-smart-client-into-my-database#comment6</guid><pubDate>Thu, 19 Apr 2007 14:00:20 GMT</pubDate></item><item><title>Ayende Rahien commented on Who let that smart client into my database?</title><description> @Shane,
  
What ken said :-)
</description><link>http://ayende.com/2320/who-let-that-smart-client-into-my-database#comment5</link><guid>http://ayende.com/2320/who-let-that-smart-client-into-my-database#comment5</guid><pubDate>Wed, 18 Apr 2007 20:40:09 GMT</pubDate></item><item><title>Ken Egozi commented on Who let that smart client into my database?</title><description>@Shane:
  
The client should anyway send a request through the network, and the server should respond. The time-consuming part of the thing is in the network transport phase, no matter what protocol you are using.
  
You could possibly make it faster by doing a better serialization, which most of the time means that you lose the crappy SOAP envelope, and actually the whole XML thing altogether, and use an efficient schema for the messages you send back and forth.
  
</description><link>http://ayende.com/2320/who-let-that-smart-client-into-my-database#comment4</link><guid>http://ayende.com/2320/who-let-that-smart-client-into-my-database#comment4</guid><pubDate>Tue, 17 Apr 2007 19:37:06 GMT</pubDate></item><item><title>Ayende Rahien commented on Who let that smart client into my database?</title><description>Can you bring a use case for this?
  
I can't even imagine a case that direct DB access would be preferable to WS from performance point of view.
  
  
I don't like it because it means that my server side API is ODBC, not the friendliest to work with 
</description><link>http://ayende.com/2320/who-let-that-smart-client-into-my-database#comment3</link><guid>http://ayende.com/2320/who-let-that-smart-client-into-my-database#comment3</guid><pubDate>Tue, 17 Apr 2007 17:52:39 GMT</pubDate></item><item><title>Shane Courtrille commented on Who let that smart client into my database?</title><description>What is your reasoning for not liking direct access between an application and the database?  What do you do where performance of web services is unacceptable?
</description><link>http://ayende.com/2320/who-let-that-smart-client-into-my-database#comment2</link><guid>http://ayende.com/2320/who-let-that-smart-client-into-my-database#comment2</guid><pubDate>Tue, 17 Apr 2007 17:03:49 GMT</pubDate></item><item><title>Steve Gentile commented on Who let that smart client into my database?</title><description>Good topic.  This has been something I've had to do on my last couple of projects.
  
</description><link>http://ayende.com/2320/who-let-that-smart-client-into-my-database#comment1</link><guid>http://ayende.com/2320/who-let-that-smart-client-into-my-database#comment1</guid><pubDate>Tue, 17 Apr 2007 12:22:24 GMT</pubDate></item></channel></rss>