Re: WO & Background Services
Re: WO & Background Services
- Subject: Re: WO & Background Services
- From: steve stout <email@hidden>
- Date: Sat, 22 May 2004 02:02:19 -0700
I've been working on two projects that have a requirement like yours.
One of them needs to export some data every 10 mins to a text file and
then FTP that to another server. The other generates some jpeg images
from information in a database and sends that off to a digital signage
system a few times a day. Both have other web front ends.
If you're using WO/EOF for the web portion, there's no reason you can't
use EOF for the backend as well. You can use the EOF libraries outside
of a WO app just fine. You just need to do a little extra work to
setup the EOModelGroup and stuff like that. Then you can place all
your common EOs and other classes in a framework that can be used by
the WO app and the backend utilities.
Instead of trying to setup the models and stuff correctly to use EOF
outside of a WO app, what I've done with the 2 projects I'm working on
is just create another WO app, but in the Application constructor call
the methods that need to run and when they're done call System.exit().
It may not be the best way of doing it, but it works and it means that
WOBootstrap loads all your frameworks so you don't have to futz around
with the classpath. And all your models are loaded without any extra
work. The only thing you need to do is make sure that it doesn't try
to register itself with JavaMonitor.
The other nice thing about making it a web app is that you can comment
out the System.exit() in the constructor and create regular
WOComponents to do testing so you can see the data you're working with
easily in a web browser.
Hope that helps.
.steve
On May 21, 2004, at 7:13 PM, Lotsa Cabo wrote:
I am asking this here to determine the next logical step, from the
viewpoint of seasoned WebObjects developers.
My web application has two primary pieces: a web-based front end for
users to manage//modify settings and a back end service to perform
various offline functions. I have decided to use WebObjects, EO, and
Java for the front end. I am curious where I should look to build the
back end piece.
The basic requirements for the back-end piece are as follows:
1. Must either be a service/daemon with a timer or be able to be
spawned at certain intervals to perform its job;
2. Must be able to read/write to/from the same database as the front
end;
3. Will be parsing large amounts of small text-based files; and,
4. Multiple instances of this module will reside on other servers to
help distribute the workload.
Is there some way to leverage all of the work that will go into the web
front end on the back? Any info, advice, or opinions would be greatly
appreciated.
Thanx,
Ryan
_________________________
Tired of spam? Signup for a FREE SpamJammer.Com account and say
goodbye to junk email forever!
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.