Hi Mark --
> I see. So the design question here is: Which parts of my
> application are
> logically distinct? Then I could pull apart the pieces that are less
> interdependent. Using your theoretical design above, would
> you then have
> 13 instance scripts, one for each module? Or one instance script with
> some glue that selected the right module to use? I'd be
> interested in an
> example.
I would have 13 separate instance scripts -- one for each application
module. The separate applications would be "connected" via HTTP requests.
In other words, the HTML from one application run-mode contains links into a
other applications, via anchors and <form> actions:
<h1>Widget Detail Viewer</h1>
<b>Widget ID: 123</b>
<a href="view_related.pl?wid=123">View Related Widgets</a>
<a href="pending_orders.pl?wid=123">View Pending orders for this
widget</a>
<form action="notify_customers.pl">
<input type="hidden" name="wid" value="123">
<input type="radio" name="when" value="now">Right Now
<input type="radio" name="when" value="later">Later
<input type="submit" value="Notify Customers">
</form>
If you will pardon my contrived example, this is now multiple applications
are organized as one seamless whole for the user.
-Jesse-
--
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Jesse Erlbaum ....................... CTO
[EMAIL PROTECTED] ............. Vanguard Media
v: 212.242.5317 x115 ...... New York City
+-+-+-+-+-+- http://www.vm.com/ +-+-+-+-+-+-+
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
