T
Tim Kuehn
Guest
My thoughts: If the service's behavior doesn't change after a prior call (ie does not persist state) then the implementation is already immutable. If the service persists some state after it's called and that state could/will affect the behavior of follow-on calls, then you need to make a copy of the service and return the copy -or- separate out the functionality which persists the service's state and give the calling code a copy of that while retaining the state-free part of the code as the core of the service.
Continue reading...
Continue reading...