However there will be cases in which I (or others) will need to use these libraries in building a monolithic standalone application and I need to ponder the implications.
Dar,
There is one issue of which I am aware and for which I have no a satisfactory solution:
sharing library handlers that manipulate declared local variables.
Ideally, one could place a library stack on a network and have its resources available to every Revolution standalone running on the network. This will not work for SDB client standalones, because SDB handlers in the library stack expect the values in the library's declared local variables to persist between calls.
To this point I've just shrugged it off with "OK, each SDB client standalone will have to have its own library stack." However a solution to this issue would be really slick: imagine updating the operation of every Revolution standalone on every workstation on the network by changing a single handler & resource library stack on one workstation!
Rob Cozens CCW, Serendipity Software Company http://www.oenolog.net/who.htm
"And I, which was two fooles, do so grow three; Who are a little wise, the best fooles bee."
from "The Triple Foole" by John Donne (1572-1631) _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
