Deepal- there's no difference between having multiple configs and a
single
config in terms of the cost of having the WSDLs in memory etc.. If
there
are n services there are n WSDLs -
The problem is each single config will have n number of wsdls so , if
we
have m number of users then we
Jonathan Marsh wrote:
Deepal- there's no difference between having multiple configs and a
single
config in terms of the cost of having the WSDLs in memory etc.. If
there
are n services there are n WSDLs -
This is not an issue for the Mashup Server (At least at the moment)
because we do not
Sanjiva Weerawarana wrote:
Keith Chapman wrote:
How can I have 2 axis services both with the name sudoku? Axis disallows
this at present which pushes us to use something like jonathan-soduku
and keith-sudoku.
Nahh .. you can control all of that in Axis2.
I can have jonathan-soduku and
Sanjiva Weerawarana wrote:
Keith Chapman wrote:
Sanjiva Weerawarana wrote:
The right solution is to use a different Axis2 configuration for each
user- there's absolutely no problem doing that.
Will that scale well? (Say we have a 100 users)
Its just an object with a bunch of hashtables ..
: [mashup-dev] Some thoughts on the scripts folder,
paths,
and urls
Jonathan Marsh wrote:
to differentiate between two services with the same service name
(channa/sudoku and jonathan/sudoku).
You mean we'd need to do some front-end rewriting of the url:
/jonathan/Sudoku
to something
] [mailto:[EMAIL PROTECTED]
On Behalf Of Glen Daniels
Sent: Saturday, December 08, 2007 6:17 AM
To: mashup-dev@wso2.org
Subject: Re: [mashup-dev] Some thoughts on the scripts folder, paths,
and urls
Jonathan Marsh wrote:
to differentiate between two services with the same service name
(channa/sudoku
