SCOUG-Programming Mailing List Archives
Return to [ 12 | 
July | 
1998 ]
 
 
 
Content Type:   text/plain 
Sorry it's been so long since I've posted anything.  Since there were so many good ideas at our last   
meeting, I've had a hard time getting my arms around the ideas to bring them together.  
 
Here is what I think represents a balance between elegance, functionality, ease of implementation,   
flexibility, etc.  
 
As a function of configuration (still to be completely defined), the user will list three elements for   
each directory: Access (read/write/upload/delete), local file system name (i.e. c:\ftp), user file system   
name (i.e. /ftp).  
 
When a user changes directories, it can be compared to the list of the third attribute.  When the user   
sends or recieves a file, a similar process can be applied.    
 
The only significant open issue in my mind is what does the user's root directory look like.  I think   
the answer is that it is a composite of the base directories of all of the directories listed  for the user.    
An example:  
 
Read	C:\ftp 	/ftp  
Write	c:\ftp\upload 	/ftp/upload  
Write	c:\John		/john  
Submit	C:\Submit		/ftp/submit  
Read 	c:\pub		/pub  
 
So if the user did a DIR / he would see:  
 
/ftp  
/john  
/pub  
 
 
 
Comments?  Thoughts?  Objections?  
 
 
 
=====================================================  
 
To unsubscribe from this list, send an email message  
to "steward@scoug.com". In the body of the message,  
put the command "unsubscribe scoug-programming".  
 
For problems, contact the list owner at  
"rollin@scoug.com".  
 
=====================================================  
 
  
Return to [ 12 | 
July | 
1998 ] 
  
  
The Southern California OS/2 User Group
 P.O. Box 26904
 Santa Ana, CA  92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group.  ALL RIGHTS 
RESERVED. 
 
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International 
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
 
 |