[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ossig] Microsoft Transaction server
- To: ossig@xxxxxxxxxxx
- Subject: [ossig] Microsoft Transaction server
- From: BIGrat <tikus.besar@xxxxxxxxx>
- Date: Fri, 12 Nov 2004 05:32:08 +0800
- DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=NiHQt31F6kF/q+nZnNycguzNtv7LI2Qj8vY4ShVC4uEF4musZUWA6OkhVKYOwK3VxhzsUAT9EVLUpYXOinBF/wdAdR/ZMQuUdXStqfC7Xj9qhDougRLizqvb3TF5CzXOWrtS0gBY9NgagQxZsoSxFe04T4x0qQpK2u6V5u7aPXg=
- Reply-To: ossig@xxxxxxxxxxx
- Sender: owner-ossig@xxxxxxxxxxx
guys
i need some help here. one of my clients has decided to switch from a
JBoss/mySQL/linux solution to a M$ Transaction Server/M$SQL/Win2003Svr
solution. apart from the obvious M$ business arguments, any specific
pointers about the technical demerits of the M$ solution; in
particular M$ transaction server? my knowledge in M$ products is near
zero.
the app is web based and business critical over the net.
development tools are java vs asp.
tks
---------------------------------------------------------
To unsubscribe: send mail to ossig-request@mncc.com.my
with "unsubscribe ossig" in the body of the message