[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: inheritable file system objects, part 1: security
- To: Rob Rodgers <rsrodger@wam.umd.edu>
- Subject: Re: inheritable file system objects, part 1: security
- From: Scott.Lemon@network-integration.com (Scott C. Lemon)
Rob Rodgers wrote: > [stuff deleted] > If you can manipulate files, you can blow them away. Java is next to > useless because of the inability to store files locally. Security > capabilities don't mean anything if people don't use them, and *consumers* > using *consumer devices* wont be doing ss, they'll be storing their files > wherever. I'm not sure that I agree with part of your statement above. When you indicate that "Java is next to useless because of the inability to store files locally." I'm not sure what your definition of "locally" is. My perception is one of time and accessibility ... so locally doesn't mean the same as "on my local hard drive." I'm not sure that in the near future I want my files on my local storage device ... I want my data and information available to me where ever I might be in the world. So Java actually meets my requirements (and so does Inferno, which I currently prefer) by providing almost transparent access to resources from anywhere. When I click "File->Save" in an application, all I'm really concerned with is that I can later click "File->Open" and access that information. I would almost rather that someone else provide replication, caching, back-up, and global availability of my information ... with me granting access controls. I believe that consumers will also expect this of their "intelligent appliances" as they begin to use them. We are currently working on several projects that follow this model of client server development. If you look at the progression from SMTP to POP3 to IMAP4 you see that the data/message store has moved further and further from me and my "desktop." With Java or Inferno, that "desktop" could be my home PC, a Java terminal in a waiting room, or an Inferno phone at the airport. I think that ISPs will discover the power of services that they can offer in globally accessible storage. It will become yet another utility that we have ... just like the gas bill, the water bill, the cable bill, there will be the net bill. > Security is available today, if you want it. > Consumers don't use it when it's available. > : Inferno will not be any safer in practice than anything else. Agreed. It's the whole model that has to change to support the easy access to these capabilities in a way that is transparent to the consumer. > RSR Scott C. Lemon Network Integration, Inc. ------------71FC3C5B4B650 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii <HTML><BODY> <DT>Rob Rodgers wrote:<BR> > <BR> <BR></DT> <DT>[stuff deleted]</DT> <DT> </DT> <DT>> If you can manipulate files, you can blow them away. Java is next to<BR> > useless because of the inability to store files locally. Security<BR> > capabilities don't mean anything if people don't use them, and *consumers*<BR> > using *consumer devices* wont be doing ss, they'll be storing their files<BR> > wherever.<BR> <BR></DT> <DT>I'm not sure that I agree with part of your statement above. When you indicate that "Java is next to useless because of the inability to store files locally." I'm not sure what your definition of "locally" is. My perception is one of time and accessibility ... so locally doesn't mean the same as "on my local hard drive." I'm not sure that in the near future I want my files on my local storage device ... I want my data and information available to me where ever I might be in the world. So Java actually meets my requirements (and so does Inferno, which I currently prefer) by providing almost transparent access to resources from anywhere. When I click "File->Save" in an application, all I'm really concerned with is that I can later click "File->Open" and access that information. I would almost rather that someone else provide replication, caching, back-up, and global availability of my information ... with me granting access controls.</DT> <DT> </DT> <DT>I believe that consumers will also expect this of their "intelligent appliances" as they begin to use them. We are currently working on several projects that follow this model of client server development. If you look at the progression from SMTP to POP3 to IMAP4 you see that the data/message store has moved further and further from me and my "desktop." With Java or Inferno, that "desktop" could be my home PC, a Java terminal in a waiting room, or an Inferno phone at the airport.</DT> <DT> </DT> <DT>I think that ISPs will discover the power of services that they can offer in globally accessible storage. It will become yet another utility that we have ... just like the gas bill, the water bill, the cable bill, there will be the net bill.</DT> <DT> </DT> <DT>> Security is available today, if you want it.<BR> > Consumers don't use it when it's available.<BR> > : Inferno will not be any safer in practice than anything else.<BR> <BR></DT> <DT>Agreed. It's the whole model that has to change to support the easy access to these capabilities in a way that is transparent to the consumer.</DT> <DT> </DT> <DT>> RSR<BR> <BR></DT> <DT>Scott C. Lemon</DT> <DT>Network Integration, Inc.</DT> <DT> </DT> </BODY> </HTML> ------------71FC3C5B4B650--
- Prev by Date: Re: inheritable file system objects, part 1: security
- Next by Date: Re: any Israeli companies doing Inferno
- Prev by thread: Re: inheritable file system objects, part 1: security
- Next by thread: Re: inheritable file system objects, part 1: security
- Index(es):