On 6/15/05, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote: > > Am 15.06.2005 um 08:54 schrieb Stephen Deasey: > > > > How will you load modules at startup? dlopen() etc. take a file name. > > > > I will start with this and see if it suffices: > > Tcl_FSLoadFile dynamically loads a binary code file into > memory and > returns the addresses of two procedures within that file, if > they are > defined. The appropriate function for the filesystem to > which pathPtr > belongs will be called. If that filesystem does not > implement this > function (most virtual filesystems will not, because of OS > limitations > in dynamically loading binary code), Tcl will attempt to copy > the file > to a temporary directory and load that temporary file.
Oh, that'll work. How about registering your own handler on /* just as the core server does at startup? That way the fastpath code won't be called unless you explicitly call it. You can send files using Ns_ConnSendChannel().
