I do understand the advantages to that approach, Nick. But that was also the thinking of those who prepared the current industry benchmarks by locking in on SQL. My concern was that if you specify technologies, you can make it difficult for solutions that are outside the box. --dawn
On 7/16/07, Nick Cipollina <[EMAIL PROTECTED]> wrote:
If the consumer of this data is going to be external, then I would definitely use web services. Using a standard format (SOAP) will make it possible for anyone to consume the data. Thanks, Nick Cipollina -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dawn Wolthuis Sent: Monday, July 16, 2007 4:58 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] UniData 7.1 vs. MS SQL 2005 performance 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.
<snip> ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
