4 Jan 2002 Status report -------------------------- > In general, Kaboodle MUST be able to act as a gateway to > services running on non-Kaboodle machines. That's its whole reason > for being. It's sounds like we missed the target a little bit; > please let me know by how much!
See 29 nov 2001 Status report: http://www.geocrawler.com/archives/3/16728/2001/11/0/7196756/ Here, a scheme is described similar to the gateway, which we implemented at the early stage of development. Taking into account that experience, maintaining a VNC gate will take us 4-5 weeks after you provide us with the full specification. So, to close the first stage of the project, we should do the following things: 1. VNC Server auto-detection: OL> I suggest the following solution. The device list shows OL> special icons for the machines on which the checkbox is set so OL> to run VNC Server on startup. The existing Kaboodle algorithm of OL> LAN auto-detection is used to deliver this additional yes/no bit. 2. Complete the User Interface. Delivery date: January 21, 2002. The next project stage will include: 1. Single steel-tube for all the Kaboodle traffic (we believe this must be done in the first place); 2. SSL Transport layer; 3. New authentication layer; 4. VNC Gateway. Looking forward to hearing from you about that. _______________________________________________ Kaboodle-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
