[Starkit] Tequila T2 ?'s

[Jean-Claude Wippler]

Brian Theado wrote:

> % package require tequila
> 2.02
> % set c [tequila::rpc 127.0.0.1 18396]
> rpc0
> % $c send puts hi
> % $c send puts [glob *]
> % $c send puts [exec cmd.exe /c dir]
> % exit
>
> In all calls to send, the first window shows that all the commands run
> without complaint.
>
> sdx version tequila.kit:
> 2005/03/15 15:47:19  14876-12477  tequila.kit

Believe it or not, that's by design.  I have a version here which  
intercepts calls and allows only specific ones.  Other options are  
safe interps, and chroot jails (look for safekit on the wiki).  And  
then there's the option to layer socket-level connect/encryption  
security.

Tequila is infra-structure stuff - to me that means two things: a  
toolbox full of functions from which you can pick what you need, and  
sample software where specific approaches are worked out in more  
detail so we can build up best practices.

Tequila 2.02 is a first step.

To answer Mike Collins original Q's:

Adding extra fields is a matter of setting them, they automatically  
extend the collection structure.  The class poolMgr is an  
experimental step towards (as the name says) managing multiple pools  
- much of this is still exploration, really.  There's still an issue  
with how to store multiple pools on the server which I haven't  
resolved properly.

As for startup time: connects are async, so they shouldn't hold up  
the app as a whole, although certain apps won't be able to do much  
until the connect completes.  In 2.02, the entire pool is sent on  
startup, so that can definitely dog down initialization.  i intend to  
address this in T3 later this year, by having clients cache copies of  
the data and sync-on-connect instead.

Keep in mind that T2 is a design phase, aimed to flesh out the API.   
And to find out about any concerns (and objections) you may have, to  
make sure there is a solution in sight.

-jcw