Am 25.11.13 23:47, schrieb Ian Harding:
That's enough to get me past this hurdle. I am not sure this is the
right path...
my recommendation is to get an in depth understanding
about the application specific performance implications of
- the general performance characteristics (per-query respon
You could try nsv to manage the list of handles, but you'd need to still
abide by the db handle lifecycle, but that's TCL code.
2013/11/26 Ian Harding
> That's enough to get me past this hurdle. I am not sure this is the right
> path... I think we could make more money by doing less slicing an
That's enough to get me past this hurdle. I am not sure this is the right
path... I think we could make more money by doing less slicing and dicing
of data in TCL and more in the database.
Thanks!
On Mon, Nov 25, 2013 at 1:16 PM, Jeff Rogers wrote:
> Ian Harding wrote:
>
>> I have a mountain
Ian Harding wrote:
> I have a mountain of code in TCL, and I am thinking of rewriting some of
> it in C.
>
> In a C module I have a function that is registered to an URL. Like I
> said, I have a bunch of TCL code that I would like to be able to use
> until (if ever) it gets rewritten.
>
> I see tha
I have a mountain of code in TCL, and I am thinking of rewriting some of it
in C.
In a C module I have a function that is registered to an URL. Like I said,
I have a bunch of TCL code that I would like to be able to use until (if
ever) it gets rewritten.
I see that I can execute TCL code and get
