add internal logic for sending replies as signals
    
    Some clients might need method replies to be sent as signals because
    they don't want to increase their timeouts on long-running jobs, and for
    some reason running the call async on their end is not an option.  We
    probably don't want to always do this, because it could be a lot of data
    to be sending twice, so it's disabled for now.