From petasisg at yahoo.gr Sun Dec 11 14:17:39 2016 From: petasisg at yahoo.gr (Georgios Petasis) Date: Sun, 11 Dec 2016 16:17:39 +0200 Subject: ANNOUNCE: ecap-tcl v 0.1 Message-ID: <180e96ec-ba1f-a3eb-a0c2-2a9ebc838c93@yahoo.gr> Hi all, I have created a new package, which is an eCAP adapter for the Tcl language (http://www.tcl.tk). With ecap-tcl you can adapt content with code written in Tcl. It can be found at the GitHub (BSD license): https://github.com/petasis/ecap-tcl Regards, George Petasis From rousskov at measurement-factory.com Sun Dec 11 21:49:29 2016 From: rousskov at measurement-factory.com (Alex Rousskov) Date: Sun, 11 Dec 2016 14:49:29 -0700 Subject: ANNOUNCE: ecap-tcl v 0.1 In-Reply-To: <180e96ec-ba1f-a3eb-a0c2-2a9ebc838c93@yahoo.gr> References: <180e96ec-ba1f-a3eb-a0c2-2a9ebc838c93@yahoo.gr> Message-ID: <2b55e223-87c7-452c-9d66-10957fc6271e@measurement-factory.com> On 12/11/2016 07:17 AM, Georgios Petasis wrote: > With ecap-tcl you can adapt content with code written in Tcl. > https://github.com/petasis/ecap-tcl An eCAP Tcl wrapper is a valuable contribution, thank you! If you do not mind, I will add a link to your Github project from the e-cap.org site. FWIW, it was not clear to me what the current limitations of the wrapper are: Can Tcl adapters utilize all APIs offered by the official C++ eCAP library? Please consider documenting that if you have not already. For example, it was not immediately obvious to me whether the Tcl wrapper already supports asynchronous message analysis documented in libecap/doc/async.txt and illustrated by the official adapter_async sample adapter. Thanks again, Alex. From petasisg at yahoo.gr Mon Dec 12 14:39:15 2016 From: petasisg at yahoo.gr (Georgios Petasis) Date: Mon, 12 Dec 2016 16:39:15 +0200 Subject: ANNOUNCE: ecap-tcl v 0.1 In-Reply-To: <2b55e223-87c7-452c-9d66-10957fc6271e@measurement-factory.com> References: <180e96ec-ba1f-a3eb-a0c2-2a9ebc838c93@yahoo.gr> <2b55e223-87c7-452c-9d66-10957fc6271e@measurement-factory.com> Message-ID: <533ac9bd-7305-3903-285d-cf8c39704749@yahoo.gr> On 11/12/2016 23:49, Alex Rousskov wrote: > On 12/11/2016 07:17 AM, Georgios Petasis wrote: >> With ecap-tcl you can adapt content with code written in Tcl. >> https://github.com/petasis/ecap-tcl > > An eCAP Tcl wrapper is a valuable contribution, thank you! If you do not > mind, I will add a link to your Github project from the e-cap.org site. Of course, please add the link. > > FWIW, it was not clear to me what the current limitations of the wrapper > are: Can Tcl adapters utilize all APIs offered by the official C++ eCAP > library? Please consider documenting that if you have not already. Right now, adapters written in Tcl can receive 5 "events": |wantsUrl, ||actionStart, | |contentAdapt, ||contentDone, ||actionStop. From these they can see/change/remove headers. | > > For example, it was not immediately obvious to me whether the Tcl > wrapper already supports asynchronous message analysis documented in > libecap/doc/async.txt and illustrated by the official adapter_async > sample adapter. I am sorry, I was not aware on these resources. When I started (some months ago), I found a sample adapter that was changing some strings in the content (had a victim and replacement). I based ecap-tcl on this. So, no it does not support asynchronous message analysis. (I have used the packages for Fedora 23/24, and the doc folder is not there). What I tried to do, is to start a number of Tcl threads, and try to distribute load to these threads, ensuring that all requests related to the same action, end up in the same thread. I will try to read the new sample adapter, and see if I can update ecap-tcl. BTW, here is a ecap-tcl in action: http://s864.photobucket.com/user/petasis/media/ecap-tcl/ecap-tcl-in-action.png.html It applies some linguistic processing on pages using Tcl code... George -------------- next part -------------- An HTML attachment was scrubbed... URL: