Re: Java Client beginner question
Re: Java Client beginner question
- Subject: Re: Java Client beginner question
- From: Ricardo Strausz <email@hidden>
- Date: Fri, 7 Feb 2003 20:11:16 -0600
Hi Kenny and all!
On miircoles, febr 5, 2003, at 16:32 America/Mexico_City, Kenny
Sabarese wrote:
i'm new to java client web objects, i have 5.2 on osx and am trying to
develop a simple 3 tier app to be used over the net.
i'm just having a bit of confusion when setting up my EOModel and
setting attributes to be client side or server side class properties.
Take a look to page 112 (and backwards) of "Java Client Desktop
Applications" for a simple examle of what properties to put in the
client and which not.
my idea is that in a 3 tiered app is that the client never talks to the
database directly. it will request things from the server which then
supplies the client with the information it requests.
but when i give an attribute client side class properties, it seems to
me as if this is enabling the client to directly access the database,
as the query window allows me to that comes up allows me to browse and
add records, but does not when i turn off client side properties.
so am i right when i say that adding client side properties allows the
client direct access to the DB? and if i want to build a thin client
application, i will have to code things myself?
No. The client never talks directly to the db, but thru the server.
I suppose that you mean by "thin" that it has as less code as possible.
If so, you may be aware becouse it is best to have as much logic in the
client as possible (to avoid being hiting the server all the time). The
most you can do on the client side, the best performence you will get.
i want a thin client in order to achive the best performance over the
internet. so say instead of the client having to go find the results
of a query itself instead of just asing a server for a list of strings.
(i would assume that the second way would consume less bandwidth)
Do not use JavaClient in the internet !!!!!! it is not done for that.
You will get a VERY slow app, no mather what you do.
If your clients are OSX machines, you can use Cocoa/EOF insted
(eventhough it is not supported by apple).
If you do not know your clients (or you know they are not OSX machines)
beter use WO apps...
I know, a browser is not the most beutyfull interface but it works...
some how.
If any how, you insist in use Javaclient thru the internet, you most be
aware that you will have to write lots of lines of code to avoid to hit
the server as much as possible (e.g., to avoid auto-sinc with the db).
Suerte!
Dino
http://homepage.mac.com/strausz
_______________________________________________
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.