I'm a researcher in an italian university and my first
field of interest now is the treatement of bioelectric signals.
I started to use Tcl/Tk as a tool language for various
tasks required in the data and system management in our lab.

I'm actively mantaining [Rivet], an Apache module
that allows Tcl scripts to be embedded in html pages, in the same
fashion PHP does.

Starting from 2006 I developed in the spare time an Itcl based
framework for building websites. This project was meant 
as a way to become acquainted with web programming, its
issues and technologies.

A few years ago I developed for a while software for the 
building automation, an application field usually not considered 
to be Tcl's turf. 

Working in this field I developed an Itcl class library that 
uses xml documents as descriptors of a communication protocol and 
of the internal resources of a PLC system. 

Exploiting the asynchronous capabilities of Tcl/Tk I wrote a server 
application that gathers data from various PLC, works as abstraction 
layer and serves the collected data to graphical interfaces for display 
and user interaction. Everything was written in Tcl/Tk using a Linux system 
and was installed on windows machines with a minimum effort for handling 
the incompatibilities (10/15 lines of code vs over 10.000 lines of the 
whole client-server application)

Notice that none of the interfaced PLC systems could handle multiple
sessions. The Tcl server worked as a multiple session handler 
endowing these interfaces of a capability which they were not
designed for.



----
!!!!!!
%| [Category Person] |%
!!!!!!