----- Original Message ----- From: "Doug Davis" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, September 30, 2002 6:16 PM Subject: RE: Dynamic publishing
> > > > > > Sorry - missed that, but why would you really want to deploy one service > per account? That's going to be a scalability nightmare. Why not just > have the account number in a soap header, as a param on an rpc call or even > in the URL (ie. > http://localhost:8080/axis/services/BankServices?account=12345 - to the > client the URL is just a string so adding on ?account=12345 should be no > big deal). > -Dug -what about session specific urls; after a logon you get a new endpoint that is valid for a while? -what about including it more in the url? http://localhost:8080/axis/accounts/12345/current Here an instance should be creatable on the fly, rather than having to prestock the system. My own use case would have urls like printqueue/entryid/13344994/ ....the limit on scalability is not axis but HDD capacity for the print queue.
