Thanks. The servant locator may not even be neccessary since i can get the information from the "current" parameter which to each operation on the server side. I get sufficient information from current.con.toString(). I'll work with that. Thanks for the suggestion of servant locators however, I think it'll even help to differentiate servant locators based on categories and designate one per each type of "user agent" so to speak. So since the applications will vary per implementation language, the servant locators should vary for each by the category. This will definitely do.
"Nothing is gained without sacrificing something of equal value..." Principles of Life: Equivalent Trade
ŪNetŪ