[e-lang] Microsoft's laws of identity
john.carlson3 at sbcglobal.net
Mon Jul 25 12:55:16 EDT 2005
I don't think that using E would help with the problem I described (I'm
fairly sure it does have the same problem). Go ahead and use Java. You
may want to consider how much security you want to put on the client
(you may want to make it a web client). Just be aware that you
shouldn't pass any capabilities to the client that you don't want the
caller of the client to have. I doubt if this will be a problem in your
Andy Dwelly wrote:
> This is not intended as a rant against E, which in fact I'm rather
> taken with; but these are practical problems that software architects
> face at the moment who might consider using E. The best I can do is
> start to experiment with some of the underlying concepts in the hope
> that at some point in the future I'll be able to say - 'lets do this
> one in E, it will save us a lot of time and money'.
>> Don't get me wrong. I am a Java advocate. It's just that when I ran
>> across the OpenJava and Javassist (and I think JMangler), they
>> opened my eyes to how Java isn't such a secure language after all.
>> It's not the language's fault, it's Sun's implementation and delivery
>> of the language.
> e-lang mailing list
> e-lang at mail.eros-os.org
More information about the e-lang