All things are lawful, but not all things are profitable.
Knute Snortum wrote:There may be other ways to do this, but I would use sockets. Sockets is not a beginning Java concept, so I'll move the thread to the sockets forums and also to Java in General, in case there are other ways to tackle this problem.
Paul Clapham wrote:If you want a client written in Java to execute a method remotely in a server also written in Java, then RMS is a Java tool which allows you to do that. (Also not a beginning Java concept.)
Dave mann wrote:RMS = Record Management System ? thats what I am getting on search engine, or not ?
Paul Clapham wrote:
Dave mann wrote:RMS = Record Management System ? thats what I am getting on search engine, or not ?
Sorry... too much Christmasery has dulled my brain today. RMI is what I should have said.
But I think it would be a good idea at this point to ask -- why do you want to do this particular thing?
(It often happens that people are trying to do something which looks like it's off the wall because they're really trying to do something ordinary but have gone directly down a blind alley.)
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Moores wrote:Web services could be implemented in the form of a Java web app, yes. The JAX-RS API (the standard Java API for RESTful web services) makes that fairly easy. "web app" in this context has nothing to do with HTML etc. - which I guess you mean by "web programming".
Tim Moores wrote:Well, RMI is a fairly low overhead approach to getting Java code to run on a remote host. If the port issue is no problem, and you have never had to deal with Java web apps (and the related servers like Tomcat), then RMI is probably the simpler approach.
But in general, RMI has fallen out of favor and been replaced with web services, implemented in Java or some other language. Just something to keep in mind going forward.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
All things are lawful, but not all things are profitable.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Knute Snortum wrote:I haven't used RMI a lot, but I would imagine that posting to a database would be a restricted activity. Allowing a remote system to update your database seems like a security risk.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Holloway wrote:Well, that's interesting. This is the first I'd heard of being able to run RMI over SSL.
The approach you mentioned will prevent external listeners from snooping over an RMI connection, but you'll also want to incorporate some sort of mechanism to identify which user is which. And ideally to limit who can connect, although there's a lot of "security through obscurity" with RMI/SSL simply because almost nobody would expect to see such a thing.
Dave mann wrote:very nice, but I still stuck in the Security problem though, Now Sockets look easier.
Dave mann wrote:...I still stuck in the Security problem though, Now Sockets look easier.
All things are lawful, but not all things are profitable.
Knute Snortum wrote:
Dave mann wrote:...I still stuck in the Security problem though, Now Sockets look easier.
Well, you'll have to deal with SSL if you use sockets too.
Dave mann wrote:I dont know how to properly disable or ( Not to Use ) Security Manager, or how to deactivate it or exclude it from RMI...
Paul Clapham wrote:
Dave mann wrote:I dont know how to properly disable or ( Not to Use ) Security Manager, or how to deactivate it or exclude it from RMI...
So have you tried modifying the policy file to permit the actions it's presently not permitting?
Those are the largest trousers in the world! Especially when next to this ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
|