[Javanetsim-cvs] javaNetSim CVS_UPDATES.txt,NONE,1.1 TODO.txt,NONE,1.1 TODO_ru.txt,NONE,1.1

[Alexander B. <da...@us...>]

Update of /cvsroot/javanetsim/javaNetSim
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv30027

Added Files:
	CVS_UPDATES.txt TODO.txt TODO_ru.txt 
Log Message:


--- NEW FILE: TODO_ru.txt ---
DO NOT EDIT THIS FILE; INSTEAD OF IT USE TODO.txt. We're on SourceForge.NET :)!!! (Speak English, OK)
--- NEW FILE: TODO.txt ---
Known Issues
------------

*** Whole Project

1. Fix Version.java: add new developers.

*** Documentation

1. Write documentation for routing functions in ProtocolStack, IPv4, Route_Entry.
2. Change the licence to licence.txt in the headers of all source files.

*** GUI Related

1. Need to save MACs.
2. Create _normal_ route table edit form (instead of route command). Use as template EditRoutesDialog.java. Note,
that "route" command is only for ugly testing purposes!
3. Routing tables save/load.

*** Simulation Related

5. The routing tables do not support netID's or subnetID's. In fact nothing in the simulation supports net or subnet 
IDs.
8. Cannot route to another Node if sending from the Application layer of a Router (SENDAPPDATA router1 pc2 
message1 data). This would be because there's no IP Forwarding decisions on the receivePacket() method in IP when receiving a 
Packet from the upper layer (UDP). 
The Routing table needs to be checked and a decision made as to which interface to send the data to.
9. Routing tables do not contain default routes.
10. The deleteNode() and deleteLink() methods need to be tested. The deleteNode() definitely needs changing, see 
the Simulation.java source file for more details.
11. Need to design __normal__ routing tables with any number of entries.
12. 2Fedor: OSPF.
13. FDDI (Key && Gift(?))
14. Switches (?)
15. UDP (Gift)
16. TCP(Gift && Key).
17. ***IMPORTANT***: Dirty lines!!!


*** Command Line Interface (CLI) Related
(useless tasks, CLI shall be removed in future)

0. Redevelop the CLI.
1. The Command Line Interface DISPLAYNODES and DISPLAYLINKS functions do not output anything if there are no Nodes or Links in the Simulation. Same with the DISPLAYSCRIPT command, if the script is empty nothing is displayed.
2. The Command Line Interface DISPLAYALLINFO command will instantiate more than one timer if you use it more than once. This will also cause the CLI to not exit normally when using 'exit' or 'quit'.
3. In the CLI, a warning message is printed out if there are simulation network environment problems before using RUNSCRIPT. The CLI *may* fall over if you attempt to run the script when there are some environment problems. This hasn't been tested completely.


--- NEW FILE: CVS_UPDATES.txt ---
File for announce CVS updates.