|
QSA ToolWorks Public Feedback Forum forum home | register | profile | members |search | faq homepage | lost password? | chat room |
| QSA ToolWorks Public Feedback Forum > TCP/IP > The Features We Want to Include | You are not logged in. Login or Register. |
| Pages: 1 |
| Author: | Topic: The Features We Want to Include | |||
Matt![]() Posts: 107 Registered: 2003-02-16 mstrange@mac.com |
Here is the laundry list of features and issues we want to address in the TCP/IP implementation in Helix. Please comment on any particular items that are of interest to you and you believe need further refinement, or any aspects we have missed. -- 1) Public and Private IP Addresses simultaneously 2) Multiple Clients via one IP Address (DHCP/NAT) 3) Multiple IP Addresses on Server (IP Multihoming) 4) Both Client and Server can be placed behind Firewalls 5) Data Encryption 6) Simultaneous access from mixed OS Clients (Mac OS 8.6 and higher) 7) Client access via Proxy Server 8) Performance equal to or exceeding 5.1's AppleTalk routing over similar network configuration. (As per Wade Brezina's comments 9) Client needs to be able to auto-discover Server's on its local subnet (NSP or Rendezvous?) 10) Client needs to support DNS lookups to locate Server 11) Admin should have an option to hardwire the Client to automatically visit a specific Server 12) Each Client needs to be able to be configured with fixed port numbers so NAT will work. (As per Ryan Wilcox's comments) 13) Data stream compression - particularly with documents - would improve performance. (As per Ryan Wilcox's comments) 14) A Client option to defer transfer of large byte streams - similar to web browser's ability to turn off image loading. - Edited by Matt on: Apr 24, 2003 11:22:33 pm
|
|||
| Ryan Wilcox Posts: 32 Registered: 2003-04-17 |
The ability to specify _what_ bytestreams to "turn off' (ala: image loading disabling in web brwosers) would be a good thing. Say different checkboxes ('load images', 'load subforums'... I can't think of any more objects on the template there) Another nice option would be "fill in lists as data arrives" vs the current "fill in lists when all data is retrieved"). Don't know how hard the latter would be, but it would be nice (calling up a 1K record list over modems, for example)
|
|||
| lucidlee Posts: 18 Registered: 2003-04-09 |
Appropos Ryan 's suggestion for compressed data streams I think its a no-brainer that encryption should be implemented.
|
| Pages: 1 |
| Lost Password? Powered by UPB Version : 1.8 A script by PHP Outburst |