This doesn't make any sense!
If child#1 answers the 'login' call for the account and creates the account HoH in it's own child#1's address space, then how does child#4 access the information?
During testing, the children real/virtual memory didn't change, but the parents real/virtual memory expanded and contracted based upon load(number of users ). By using the in-memory hash, we increased performance significantly depending on operating system over using a DB to store the information.
Could JavaFan explanation have been accidentally activated by the way we wrote the application?
The application can't work without sharing the data between children. And the application does work!
Thank you
"Well done is better than well said." - Benjamin Franklin
In reply to Re^10: Defining global variable in a subroutine
by flexvault
in thread Defining global variable in a subroutine
by bihuboliya
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |