-- @(#)FUTURE-WORK	5.1 --

----------------------------------------------
-- Please add your suggestions to this list --
----------------------------------------------

--------------------------
	General:
--------------------------

- Simple/clean example of writing a useful OTSO protocol is
  documented.  This would be useful if we package OTSO for use
  by educational institutions for teaching students to write telecomm
  protocols.

- XWindows + User Interface (parts of this are done in the dvterm
  directory and the InterViews/dvops directory, but it is a bunch of
  loose ends that needs to be integrated together)

- Multiple connection OTSO (this has been finished by juha ?)

- Simulation OTSO (virtual time ?) this has been done by Matti Sangi at LTKK,
  we will add into the official OTSO source tree soon.

- Document use of ASN.1 in OTSO
	- someday soon - jfr

- Tran4 completed by Matti Sangi must be added to official source Tree.

- Full OSI protocol stack would be nice

- CVOPS and/or ISODE interfaces ?

- Port OTSO :
	- to OS/2
	- msdos  - zortech C++ 2.0 or Turbo C++ (eoj has done much of this)

- Multiple-computer OTSO demonstration.
	close to finished but destProcess() returns null process in
	Message::send(), ??? because of multi changes ???

- better "Dynamic" load-balancing/ object migration ?

- Use Dynamic libraries, so we have smaller executables on Sun

- Audio Device added to Dvops for fun and nice demos 
  see /otso/demo/Telephone.  Should be made more efficient:
	- OTSO efficiency should be improved
	NonBlocking Device Writes waste valuable CPU
	time! 
	- OTSO Frames are used badly in this demo,
	they should directly use a Frame char*.

- OTSO should be profiled to find potential bottlenecks
	- Juha Koivisto has started doing this.

- It might be a good idea to replace the unidirectional streams in OTSO
  with bidirectional streams (terminals).


--------------------------
	Specific :
--------------------------
