|
|
Back to UserFriendly Strip Comments Index
|
Okay, another OOP question | by MatthewDBA | 2011-01-13 06:24:48 |
|
Are you sure you are not reinventing a wheel? | by CALL-198 | 2011-01-13 09:59:17 |
|
At this point I don't have a framework selected | by MatthewDBA | 2011-01-13 10:09:06 |
| I can give a general meaning. |
by CALL-198 |
2011-01-13 10:34:40 |
I don't know how the JVM comes into play.
For native programs, each process runs within its own processes space containing its own memory which only it can access (there are ways of sharing memory segments but that is done explicitly). Any coordination done with multiprocessing makes use of IPC mechanisms or socket connections. I would suspect, that for the JVM, this means each process has its own VM instance. This is the most secure because your process, if it is hijacked, cannot gain access the internals of the authentication daemon.
All of a program's threads run within the same process space. Function calls receive their own static variables; but, global variables and the heap is shared between all threads. If any thread is hijacked, it can potentially access information from any of the other threads.
There is a third category, lightweight processes, that are sometimes created by VMs or other frameworks. Lightweight processes act like processes from a programming perspective because the VM/framework provides them with separate memory allocations. Underneath, the LWPs are actually running within a single process space with the framework scheduling them and creating the synthetic divisions between them. They are quite often, created using threads to allow take advantage of the operating systems scheduler. From a security standpoint, they are as vulnerable as threads. |
|
[ Reply ] |
|
OK, thanks. | by MatthewDBA | 2011-01-13 11:07:50 |
|
|
[Todays Cartoon Discussion]
[News Index]
|
|
