Hi Daniel,
My take is the layering is levels of responsibilities, where as the database
base is responsible for the data storage layer and quite possibly the
processing layer also. and Delphi is responsible for the Visual or GUI
presentation of the results returned by the processing layer.
Sybase can contain the entire application logic and processes in the form of
Stored Procedures, Triggers, Scheduled Events.
I have been developing a Tango/Sybase application and have seen some
remarkable processing speed of Sybase in regards to Stored Procedures, Etc.
Layer 1 Data in table
Layer 2 Constraints and Triggers
Layer 3 Stored Procedures and Functions
Layer 4 Security access rights
Layer 5 Delphi for Visual and Interaction with Client
> Oh yeah, there is an ulterior motive. I figure that once he uses Oterro,
> he'll ditch the other guys and switch to RBTI.
Good Luck, Sybase has security integrated with NT or Separate. Event
Scheduler, JAVA integration
and this could all be under the clients control and you just get to work on
the last layer (visual) and would have
to request the added functionality in the database from the clients DBA.
Ben Johansen
----- Original Message -----
From: "DanielW" <[EMAIL PROTECTED]>
To: "RBase Listserver" <[EMAIL PROTECTED]>
Sent: Tuesday, May 29, 2001 8:07 PM
Subject: What is layering?
> I was speaking with the company that developed our mission critical app at
> work, His front end was developed in Delphi with Borland's engine on the
> back. However, he insisted that he uses Sybase to manage the data. He said
> the process was known as layering.
>
> I am playing with the idea of writing a module for their system with
Delphi
> on the front and Oterro on the back, but I'm still wondering where this
> layering thing comes in. Any takers?
>
> Oh yeah, there is an ulterior motive. I figure that once he uses Oterro,
> he'll ditch the other guys and switch to RBTI.
>
> Dan
>
>
