home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Encyclopedia 96-1
/
novell-nsepro-1996-1-cd2.iso
/
download
/
netware
/
dax1.exe
/
DOC
/
ENHANCE.DOC
next >
Wrap
Text File
|
1992-03-05
|
2KB
|
39 lines
Last Update: 03/05/92
1. make DAPSend detect and SIP failure, and take appropriate action,
so application will not keep trying to send data on a failed conn.
2. Version that you register for broadcast updates on specific events.
3. Version to monitor an NLM. The NLM would make API calls that would
cause messages to be sent. Maybe even trap certain CLib calls?
4. Multi-Threaded NLM version.
WorkerBee threads will have a pointer to a structure that has
a semaphore and a pointer to a DAPDATA structure. Can pass
a pointer to a semaphore on the way in, then the worker bee
could save it, and use that pointer to dereference the DAPDATA
structure later on. this would require a static somewhere...ugly
maybe the first idea is better.
Semaphore will be the same for all occurances of the workerbee.
Need a killme flag. Maybe a pointer to it in the structure, then
if it is positive, decrement and die... Otherwise, just a variable,
and the monitor thread could kill it and reuse the structure for
the next instance.
4a. Multi-Threaded NLM client.
5. DYNAMIC vs STATIC declarations for arrays of control structures.
6. Linked list for increasing and decreasing arrays. Allocate a[20],
when full, allocate another, and udpate a control struct w/list pointer
and other things like #elements used, left, #blocks allocated, etc.
7. DOSCLI and NLMCLI constants
8. If a packet is returned to the client after the client has exited
DAPSend(), when the client attempts the next send (if he ever does),
a packet out of sequence error will occur, cause a receive ECB has
been posted with the result from the last request.