Why not Expose the internal Base64 decoding like this (in InkAPI.cc):
// Expose internal Base64 decoding
tsapi char * TSbase64Decode(const char * input, int input_len, int *output_len){
return ink_base64_decode(input, input_len, output_len);
}
tsapi char * TSbase64Eecode(const char * inpu
- Original Message -
> Why not Expose the internal Base64 decoding like this (in InkAPI.cc):
>
> // Expose internal Base64 decoding
> tsapi char * TSbase64Decode(const char * input, int input_len, int
> *output_len){
> return ink_base64_decode(input, input_len, output_len);
> }
>
Friday, December 9, 2011, 5:17:56 PM, you wrote:
> NetHandler::mainNetEvent doesn't lock the VCs because it doesn't need to
> until it wants to access the internal data at which time it locks it.
> Therefore the internal data is protected by the NetVC mutex. However, the
> existance is NOT prote
On 12/12/11 3:31 AM, Igor Galić wrote:
- Original Message -
Why not Expose the internal Base64 decoding like this (in InkAPI.cc):
// Expose internal Base64 decoding
tsapi char * TSbase64Decode(const char * input, int input_len, int
*output_len){
return ink_base64_decode(input,
> > The NetHandler lock is used to protect the allocation, deletion of
> > the
> > NetVC. The owner of the NetVC lock can set the 'closed' flag, but
> > can't
> > delete the NetVC unless they own the NetHandler lock.
>
> Sure it can, it just calls do_io_close. I direct your attention to
> HttpS
- Original Message -
> On 12/12/11 3:31 AM, Igor Galić wrote:
> >
> > - Original Message -
> >> Why not Expose the internal Base64 decoding like this (in
> >> InkAPI.cc):
> >>
> >> // Expose internal Base64 decoding
> >> tsapi char * TSbase64Decode(const char * input, int input_le
Oh, I think it was there, but *someone* of fell intent removed it. H.
Unfortunately, the list of suspects is too long to put in this message.
http://people.apache.org/~amc/images/TS-Lock-Classes.png
Monday, December 12, 2011, 10:43:17 AM, you wrote:
>> I have
>> attached a diagram of this ca
On Mon, Dec 12, 2011 at 7:21 AM, Alan M. Carroll <
a...@network-geographics.com> wrote:
> Friday, December 9, 2011, 5:17:56 PM, you wrote:
>
> > NetHandler::mainNetEvent doesn't lock the VCs because it doesn't need to
> > until it wants to access the internal data at which time it locks it.
> > T
Monday, December 12, 2011, 1:51:54 PM, you wrote:
> When I left Inktomi the inactivity timer was managed directly i.e.
> INACTIVITY_TIMEOUT was set. It looks like someone checked in an
> InactivityCop. This is protected by the NetHandler mutex. It also takes
> out the NetVC mutex in case there
