Do you control the application on the server?
Did you write it?
What *exactly* do you mean by that?
Perhaps it is better to state what you want to *achieve*
than what you want to *do*. So, what do you hope to gain
through this 'memory modification'?
The application consists of a complex schedule, that I am yet to
write. I control everything about this application. The application
sits on some server on the web.
I need ways to interface into this application via the web browser to
do two things:
a) I need to be able to run an algorithm on this schedule.
b) I need to be able to modify the schedule within the application.
I am investigating the easiest way to design/implement this.
I know I could save the schedule in a database, and have an html
frontend. I can map the html requests to operations on the schedule.
Everytime someone modifys it I can update the database. Also if I need
to run the algorithm on it, I can load the database into memory (build
the schedule), run the algorithm, return the result in html.
What I am wondering is, can I skip the need of a database, store the
schedule prepetually in memory - and have java applets (or something
similar?) that can directly access the memory of the application ?
This would help me skip the whole html part too.
I don't know if this is possible, it's just a thought I'd like to
investigate. What got me thinking along these lines, is that in Unix
we can define shared memory across processes; this would be similar
only the memory would be shared across processes on seperate machines.