Yes, agreed. I think if you start with user requirements for services, then have folks design for those requirements according to each environment, that would be a good start. I hesitate to say that it must be "web services" only because that might imply use of SOAP or an XML exchange that could prejudice the implementation, but otherwise defining the requirements as services makes a lot of sense. Each service implementation in different environments can then be judged and compared by a variety of measures.
I'm starting to get that "fear of being tossed to u2-community" vibe when typing this... Time for some chocolate, perhaps. --dawn On 7/16/07, Marc Harbeson <[EMAIL PROTECTED]> wrote:
That's why I suggested a web service method - by which each db could employ whatever methodologies they have available - where the front end could run the same transaction sets thru different back end API sets. An example API might be "Book Order" or "Ship Order" for example. I would imagine a full suite of transaction tests would also include the transactions to populate a "test" database with objects such as "Customers" "Items" etc etc. Just a thought. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geoffrey Mitchell Sent: Monday, July 16, 2007 2:47 PM To: [email protected] Subject: Re: [U2] UniData 7.1 vs. MS SQL 2005 performance How does not being able to know how the data is stored prohibit empirical testing? As long as you can provide inputs to a system and retrieve outputs you can perform empirical tests. -- Geoffrey Mitchell Programmer/Analyst Home Decorator's Collection 314-684-1062 ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
-- Dawn M. Wolthuis Tincat Group, Inc. tincat-group.com Take and give some delight today ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
