[GitHub] [trafficserver] SolidWallOfCode commented on issue #6602: TSContSchedule API renaming

[GitBox <gi...@apache.org>]

SolidWallOfCode commented on issue #6602:
URL: https://github.com/apache/trafficserver/pull/6602#issuecomment-616682942


   Given what I suggested [a month ago](https://github.com/apache/trafficserver/pull/6577#issuecomment-604720341) I am glad to see @sudheerv and @bryancall have come around to my point of view. We should have `TSContScheduleOnPool` for pool based scheduling and `TSContSchedulOnThread` for thread based scheduling. Scheduling on the current thread is then
   ```
   TSContScheduleOnThread(cont, TSEventThreadSelf());
   ```
   Which I find much clearer than just `TSContSchedule`, which I think should be reserved for purely "automatic" scheduling, in situations where the continuation came from somewhere else and it should be sent back there (via thread affinity).


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org