Comments on: Mocking the Server Side http://dave.sunwheeltech.com/wordpress/2005/10/17/mocking-the-server-side/ Dave Crane's weblog Wed, 20 Aug 2008 16:23:52 +0000 http://wordpress.org/?v=1.5.1.2 by: Pavan Keely http://dave.sunwheeltech.com/wordpress/2005/10/17/mocking-the-server-side/#comment-48 Sat, 04 Feb 2006 00:39:10 +0000 http://dave.sunwheeltech.com/wordpress/2005/10/17/mocking-the-server-side/#comment-48 This is exactly what I do...Mock the server side results with a file in the file system. This way it would be easy too to debug the issues with some part of the code. Pavan keely This is exactly what I do…Mock the server side results with a file in the file system. This way it would be easy too to debug the issues with some part of the code.

Pavan keely

]]> by: ntschutta.com » Blog Archive » More Foundations of Ajax http://dave.sunwheeltech.com/wordpress/2005/10/17/mocking-the-server-side/#comment-25 Tue, 01 Nov 2005 02:55:02 +0000 http://dave.sunwheeltech.com/wordpress/2005/10/17/mocking-the-server-side/#comment-25 [...] “mock” the server - so we were particularly interested in David Crane’s Mocking the Server Side blog. BTW, congrats on the book!) Despite th [...] […] “mock” the server - so we were particularly interested in David Crane’s Mocking the Server Side blog. BTW, congrats on the book!) Despite th […]

]]> by: AJAX » Dave Talks About Client/Server Side Code, Needs Feedback http://dave.sunwheeltech.com/wordpress/2005/10/17/mocking-the-server-side/#comment-23 Thu, 20 Oct 2005 00:23:46 +0000 http://dave.sunwheeltech.com/wordpress/2005/10/17/mocking-the-server-side/#comment-23 [...] e, Needs Feedback October 19, 2005 on 5:21 pm ¦ In AJAX Programming ¦ Dave talks about his AJAX programming ways and says: So, my general questi [...] […] e, Needs Feedback October 19, 2005 on 5:21 pm | In AJAX Programming | Dave talks about his AJAX programming ways and says: So, my general questi […]

]]> by: Phil Wills http://dave.sunwheeltech.com/wordpress/2005/10/17/mocking-the-server-side/#comment-20 Wed, 19 Oct 2005 12:52:39 +0000 http://dave.sunwheeltech.com/wordpress/2005/10/17/mocking-the-server-side/#comment-20 Seems entirely sensible to me. I've used the same technique and anything that allows you to develop and test a component in isolation before coming up against the problems of integrating it into a wider system has to be helpful. Seems entirely sensible to me. I’ve used the same technique and anything that allows you to develop and test a component in isolation before coming up against the problems of integrating it into a wider system has to be helpful.

]]> by: Thomas J Lukasik http://dave.sunwheeltech.com/wordpress/2005/10/17/mocking-the-server-side/#comment-19 Tue, 18 Oct 2005 20:07:41 +0000 http://dave.sunwheeltech.com/wordpress/2005/10/17/mocking-the-server-side/#comment-19 In the "old days" (even older than what people nowadays tend to think of as "the old days"..) we used to refer to this practice as "stubbing out the code". Anywhere that "real" code wasn't available to "take a call", we would fake it by writing a throwaway component to act like the missing code. Today, the missing code is more likely a missing service (database, HTTP, etc.) than just some unwritten logic, but I think that the idea and purpose are much the same. These days I use this technique more often to stand in for HL7 responders than XML responders, since real HL7 servers are generally not accessible, being critical medical systems well hidden behind hospital firewalls. So, generally speaking, I think that it is a useful and safe way to "move along" whenever you wouldn't otherwise be able to for lack of access to a real or simulated deployment environment to test in. In the “old days” (even older than what people nowadays tend to think of as “the old days”..) we used to refer to this practice as “stubbing out the code”.

Anywhere that “real” code wasn’t available to “take a call”, we would fake it by writing a throwaway component to act like the missing code. Today, the missing code is more likely a missing service (database, HTTP, etc.) than just some unwritten logic, but I think that the idea and purpose are much the same.

These days I use this technique more often to stand in for HL7 responders than XML responders, since real HL7 servers are generally not accessible, being critical medical systems well hidden behind hospital firewalls.

So, generally speaking, I think that it is a useful and safe way to “move along” whenever you wouldn’t otherwise be able to for lack of access to a real or simulated deployment environment to test in.

]]>