26 Sep
2013
26 Sep
'13
2:11 p.m.
On Thu 26 Sep 2013 11:08:28 AM CEST, Klaus Darilion wrote: IMO, this should be consistent too. You know what, you‘re totally right. I had a rough time setting this all up in the beginning and this one slipped through the cracks. I’ve now gone ahead and made the change to the API to use |protocol| instead of |use_tcp|. New appropriate values include |TCP| or |UDP|. *Using the old method will no longer work*, and the documentation has been appropriately updated. Thanks for catching this, and my apologies to those of you who may be using |use_tcp|. I'm sure you can all agree though that consistency is best for something like this.