This project is mirrored from https://:*****@github.com/Ensembl/zmap.git.
Pull mirroring updated .
- Mar 22, 2004
-
-
edgrif authored
-
edgrif authored
these functions must usually only be called once this is all done via a mutex protected list.
-
edgrif authored
-
edgrif authored
-
edgrif authored
common to all server implementations. Add hard-coded prototypes for functions that return function pointers for each specific server implementation.
-
edgrif authored
code which given a protocol, e.g. "das", will load the DAS routine function pointers and call them. These pointers are set up once per protocol and then reused for each subsequent connection to a server of this protocol.
-
edgrif authored
-
edgrif authored
-
edgrif authored
-
edgrif authored
have such routines and they really must only be called once. This routine also returns a void* which actually contains the function pointers for the specific server routines. Add a length to the request routine, we can't assume C strings will be returned.
-
- Mar 19, 2004
-
-
edgrif authored
-
- Mar 18, 2004
-
-
edgrif authored
-
- Mar 17, 2004
-
-
edgrif authored
-
- Mar 12, 2004
- Mar 03, 2004
-
-
edgrif authored
-
edgrif authored
-
edgrif authored
-
edgrif authored
Change code that creates a ZMap to use new ZMap calls that do this. Add code to load data into a zmap and also to reset one, the latter operation is unfinished.
-
edgrif authored
Sort out the killing of GUI and threads so they are correct for a ZMap to kill itself. Add new states to ZMap so we can better control interaction with user and with threads. Each Zmap can now run multiple threads to contact multiple servers. Make cleanup code more robust by using state of Zmap and state of threads.
-
edgrif authored
-
edgrif authored
-
edgrif authored
-
edgrif authored
-
edgrif authored
-