[Starkit] Tequila T2 ?'s

[Steve Landers]

Further to this

On 08/06/2005, at 3:43 AM, Jean-Claude Wippler wrote:

> To answer Mike Collins original Q's:
...
> 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.
>
> 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.

I've just completed an application using T2, and as JCW + Mark said -  
it is important to recognise that T2 is still raw and changing.

Having said that, it is extremely useful and (if you are willing to  
invest the time) it will help push the design forward. Just expect  
some frustrations as you get used to the new way of thinking  
(everything must be async!) and hit the limits of the current  
implementation.

As for the startup speed, the application I mention loads almost a  
megabyte of data (comprising several tables, some up to a few  
thousand rows) and startup is still fast on a local network. If you  
are seeing the application as a whole freezing then I'd suspect the  
problem is elsewhere - perhaps you are hitting some of the async  
issues I mentioned.

Re async, it's easy to trip on that one - a couple of times I built a  
small, stand-alone test script that set a property, tried to read it  
back and got nothing.  The problem was that I didn't force Tcl into  
the event loop, and so the value never propogated to the server and  
back. Be aware of that one - I'll be surprised if it doesn't get you  
at least once.

Also, I've found it best to avoid the unnamed collection for for.

HTH

Steve


--
Steve Landers                     Software Design Solutions
Digital Smarties                  steve at DigitalSmarties.com
Perth, Western Australia          DigitalSmarties.com