You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@ws.apache.org by Matthew Geis <ma...@instill.com> on 2000/12/08 18:39:43 UTC
app server question (a little off topic)
Hi -- Is anyone out there using JBoss (www.jboss.org)? Open-source J2EE app
server, looks like it has good features, etc. I just ran across it, but
haven't heard anything about it on the list or otherwise.
If anyone has a minute, could you email me (off list) at
matthew.geis@instill.com, with any thoughts/impressions, etc. Also, if
anyone can offer comparisons of how it stacks up to the competition, I'd be
grateful.
Thanks in advance.
Matt
RE: MSXML and SOAP server-side
Posted by Peter Tji <k....@chello.nl>.
I think the way to go is to compile isapi in multithreaded mode en use that
in combination with Microsoft Transaction Server and make use of object
pooling MTS offers. You may have to reprogram the current components, but it
isn't that much work.
-----Original Message-----
From: Ross Lambert [mailto:ross@webwolves.com]
Sent: Friday, December 08, 2000 11:22 PM
To: soap-dev@xml.apache.org
Subject: MSXML and SOAP server-side
Folks,
I just started contracting with a company that is developing a high-traffic,
vertical market web site. Part of the design includes accessing various
home-grown SOAP servers for information. The staff dvelopers accomplished
this using an ASP page that uses the MSXML DLL; the page packages up a SOAP
request using JScript and MSXML, sends it off to the SOAP server, and parses
and returns the result.
I am wondering if MSXML is OK to use server-side under heavy loads (likely
to be multiple thousands of simultaneous connections). They do plan on
throwing a lot of clustered hardware at this thing. But the part that
worries me is this whole process is essentially synchronous--since the SOAP
server access is done server-side, the page essentially locks up until the
SOAP server responds. This is somewhat slow even now with one connection!
I'm new to SOAP, but I've go to ask, "Is there a better way?"
I've at least got to wonder if returning a "template" page and having the
same SOAP request made client-side might not be better. The client at least
gets something quickly, and the SOAP return data can be parsed and plopped
in to things dynamically. And you take a whale of a load off the servers.
As a point of interest, they also wrote their SOAP servers using ASP and
JScript. That may be why things are slow. I'm probably washing the wrong
dog. :-)
Ross Lambert
WebWolves, LLC
RE: MSXML and SOAP server-side
Posted by Peter Tji <k....@chello.nl>.
I think the way to go is to compile isapi in multithreaded mode en use that
in combination with Microsoft Transaction Server and make use of object
pooling MTS offers. You may have to reprogram the current components, but it
isn't that much work.
-----Original Message-----
From: Ross Lambert [mailto:ross@webwolves.com]
Sent: Friday, December 08, 2000 11:22 PM
To: soap-dev@xml.apache.org
Subject: MSXML and SOAP server-side
Folks,
I just started contracting with a company that is developing a high-traffic,
vertical market web site. Part of the design includes accessing various
home-grown SOAP servers for information. The staff dvelopers accomplished
this using an ASP page that uses the MSXML DLL; the page packages up a SOAP
request using JScript and MSXML, sends it off to the SOAP server, and parses
and returns the result.
I am wondering if MSXML is OK to use server-side under heavy loads (likely
to be multiple thousands of simultaneous connections). They do plan on
throwing a lot of clustered hardware at this thing. But the part that
worries me is this whole process is essentially synchronous--since the SOAP
server access is done server-side, the page essentially locks up until the
SOAP server responds. This is somewhat slow even now with one connection!
I'm new to SOAP, but I've go to ask, "Is there a better way?"
I've at least got to wonder if returning a "template" page and having the
same SOAP request made client-side might not be better. The client at least
gets something quickly, and the SOAP return data can be parsed and plopped
in to things dynamically. And you take a whale of a load off the servers.
As a point of interest, they also wrote their SOAP servers using ASP and
JScript. That may be why things are slow. I'm probably washing the wrong
dog. :-)
Ross Lambert
WebWolves, LLC
MSXML and SOAP server-side
Posted by Ross Lambert <ro...@webwolves.com>.
Folks,
I just started contracting with a company that is developing a high-traffic,
vertical market web site. Part of the design includes accessing various
home-grown SOAP servers for information. The staff dvelopers accomplished
this using an ASP page that uses the MSXML DLL; the page packages up a SOAP
request using JScript and MSXML, sends it off to the SOAP server, and parses
and returns the result.
I am wondering if MSXML is OK to use server-side under heavy loads (likely
to be multiple thousands of simultaneous connections). They do plan on
throwing a lot of clustered hardware at this thing. But the part that
worries me is this whole process is essentially synchronous--since the SOAP
server access is done server-side, the page essentially locks up until the
SOAP server responds. This is somewhat slow even now with one connection!
I'm new to SOAP, but I've go to ask, "Is there a better way?"
I've at least got to wonder if returning a "template" page and having the
same SOAP request made client-side might not be better. The client at least
gets something quickly, and the SOAP return data can be parsed and plopped
in to things dynamically. And you take a whale of a load off the servers.
As a point of interest, they also wrote their SOAP servers using ASP and
JScript. That may be why things are slow. I'm probably washing the wrong
dog. :-)
Ross Lambert
WebWolves, LLC
MSXML and SOAP server-side
Posted by Ross Lambert <ro...@webwolves.com>.
Folks,
I just started contracting with a company that is developing a high-traffic,
vertical market web site. Part of the design includes accessing various
home-grown SOAP servers for information. The staff dvelopers accomplished
this using an ASP page that uses the MSXML DLL; the page packages up a SOAP
request using JScript and MSXML, sends it off to the SOAP server, and parses
and returns the result.
I am wondering if MSXML is OK to use server-side under heavy loads (likely
to be multiple thousands of simultaneous connections). They do plan on
throwing a lot of clustered hardware at this thing. But the part that
worries me is this whole process is essentially synchronous--since the SOAP
server access is done server-side, the page essentially locks up until the
SOAP server responds. This is somewhat slow even now with one connection!
I'm new to SOAP, but I've go to ask, "Is there a better way?"
I've at least got to wonder if returning a "template" page and having the
same SOAP request made client-side might not be better. The client at least
gets something quickly, and the SOAP return data can be parsed and plopped
in to things dynamically. And you take a whale of a load off the servers.
As a point of interest, they also wrote their SOAP servers using ASP and
JScript. That may be why things are slow. I'm probably washing the wrong
dog. :-)
Ross Lambert
WebWolves, LLC