Re: Direct or Indirect?
Re: Direct or Indirect?
- Subject: Re: Direct or Indirect?
- From: Ricardo Strausz <email@hidden>
- Date: Tue, 28 Jan 2003 19:58:29 -0600
Before trying to develop/deploy a JC app for the web, I really
recommend you to read the "When to Choose Java Client" part of the
first chapter of "Java Client Desktop Applications" book by Apple (WO
5.2 comes with a hardcopy of it). I quote (p. 28)
"It is not ideal, however, for use in uncontrolled Internet eviroments
or for high-traffic websites."
On martes, ener 28, 2003, at 17:41 America/Mexico_City, Richard Good
wrote:
Thanks for your comments. I hope I can get decent response over the
web using a java client.
On Tuesday, January 28, 2003, at 11:30 AM, Ricardo Strausz wrote:
Hola tocayo!
If you are planning to deploy in the internet (WAN), non of the
approuches wiil be a good idea.
JavaClient apps are thought of to be deployed in an intranet (LAN),
where you can control all the envairoment. If you do not have that
control, it will get a VERY slow app.
To deploy in the internet, WO offers DirectToWeb ---with its
non-direct version--- as a first approuch and then you can customize
you app as much as you want. But it will then be an "app" whose
interface is a web-browser and is "attached" to the so called
"Request-Response" loop.
Back into the `direct or non direct' dilema, the main difference is
that in the direct approuch, a "wizard" uses your EOModel (a deep
description of your database) to build an app which can acces and
modify all the entities in your db with out a single line of code. It
works preaty well for testing a Model and to create basic prototypes.
In the non-direct appreouch, you are responsible of every single
detail: the interface, the code, and so on.
In fact, the best approuch is to use a combination of both: you start
with the Direct wizard and then, step by step you customize your app
adding new interfaces and code which reflects better you paradigm.
Suerte!
On martes, ener 28, 2003, at 10:41 America/Mexico_City, Richard Good
wrote:
I'm new to webobjects and have some basic design questions. Here's a
little background on our project.
We have developed a moderately sized (100 MB of data, 8 tables
ranging
from a few hundred to a few hundred thousand records) database in
FileMaker that we access via a java program using the Filemaker java
interface (not the JDBC interface). The java program provides all
of
the user interface is mature and stable. We are investigating moving
to a different database and deployment environment as we will be
expanding and accessing the database over the internet rather than
just
locally.
We have two options open now we can replace our FileMaker access
with a
JDBC interface to an SQL database OR perhaps we could use webobjects.
If we use webobjects should we go with a indirect to java client or
direct to java client approach. With my limited understanding of
webobjects I'm guessing the indirect route would allow me to reuse
more
of my existing UI code. Any suggestions would be appreciated, thanks
for your help.
Richard Good
President, True Image
http://www.schoolid.com
Handheld security solutions for schools, industry and government.
_______________________________________________
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.
Dino
http://homepage.mac.com/strausz
Richard Good
President, True Image
http://www.schoolid.com
Handheld security solutions for schools, industry and government.
_______________________________________________
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.