David,
In my opinion you have already made the correct choice. That is to
keep them separate. If you are having data synchronization issues
that is separate. You would have exactly the same data
synchronization problems simply by running two instances of the same
web application.
First you need to fix your data synchronization problems then you can
happily run your web and client applications separately sharing your
business logic framework.
I've had some experience trying to mix web and client applications
into a single application. IMHO it's just not worth the headaches it
causes.
Here is a note warning just so you don't run into this problem
yourself like I did. DO NOT use concurrent request handing with
JavaClient applications. JavaClient expects synchronous handing of
request and will break in dramatic ways if the concurrency flag is set.
On Apr 3, 2007, at 12:16 PM, David Avendasora wrote:
Hi everyone,
Does anyone have any information, or can point me to any
information, about running both a Direct to Java Client and
standard (NOT Direct to Web) Web Client on one instance of an
WebObjects application? Right now I have them as two separate
applications, both using the core framework pointing to the same
DB. This of-course can cause problems with data-synchronization.
While running them from one application will not completely
eliminate the issues, it should mitigate them to some extent.
Thanks,
Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/robertwalker1%
40mac.com
This email sent to [EMAIL PROTECTED]
--
Robert Walker
[EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
