Miko, very cool blog post. You write; > Ok so on to implementation. So we can put this interface up in front of a > pizza hut, or in front of a Domino's pizza or in front of Bilbo's pizza in > Kalamazoo Michigan. Great! Implementation doesnt matter, these are > completely interchangeable, mission accomplished! You could even put this > interface in front of a mail slot, and the money could be immediately grabbed > and the pizza implementation could be outsourced to India.
That's great and all, but by only swapping in alternate pizza ordering service implementations in you example, are you then saying that your interface restricts your service implementation that way? Said another way, could you swap in a sandwich shop, or a shoe shop, or even, say, a filesystem ...? I think that unless you can, then you haven't truly separated interface from implementation because you've said "No, my implementations can only vary *this* much and no more, because that's all the variation in implementation that my interface permits". IMO, interface and implementation aren't completely separated until you can answer "yes" to that substitutability question. Mark. -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
