At 08:07 AM 12/21/99 -0500, [EMAIL PROTECTED] wrote:
>Where's Boris when we need him? - LOL.
Burning out... <g> Seriously I thought Daniel and Kevin did a very good job!
>First let me thank everyone who has responded to my original question of
>whether you need Jaguar and Dynamo and PFC. Lot's of good opinions out
>there. Along the same light, here is a new one.
>
>Adaptive server products (AnyWhere and Enterprise) seem to have included much
>of the processing (balancing, multi-threading, etc.) that Jaguar seems to
>have. Does this mean that by using Adaptive server products and PowerDynamo
>that I can have a stable, high-performance dynamic HTML web/application
>server environment? It appears so from the documentation. It also appears
>that you should design your application in this environment like a two-tier,
>which, if true, makes a lot of sense for efficiency, control, and reduced
>cost of development.
Adaptive Server Anywhere is the old SQL Anywhere, Adaptive Server
Enterprise is SQL Server. Both are pretty good Databases, but the
multi-threading and other performance optimization features are database
specific. The databases have come a long way, now supporting Java in
SPs. However, the world of the web is different. For example if you have
500 simultaneous user session open you might not want to have 500 database
connections. EAServer provides connection pooling where you can have let's
say 10 connection open to be shared between 500 uses as needed. The same
for component instantiation. One of the most expensive operations is
component creation. Also if a separate instance of a component is created
for each user session you may quickly use up the server
resources. Easerver allows you to have a pool of components (possibly PB
NVOs) to be shared among different user sessions. But the biggest
advantage of EAServer is that it provides language transparency. You can
deploy a PB NVO and call it from a Java component or from a Page server
script. In this case the role of the page server is simply to redirect the
output to a browser with some reformatting.
PowerDynamo is a page server. Other products that fall into this category
are Active Server Pages and Java Server Pages. Page servers operate by
filtering the HTML pages looking for the server side script, delimited by
specific tags. Once the script is found it gets executed on the server
and if any output is generated it is written back to the HTML page which is
then sent to the browser. Page servers typically provide database
connectivity and access to components and limited performance tuning
features, but no advance features which can be found in Application Servers.
It is possible to build a robust web application if you don't plan to
handle a heavy transaction load with support for a *lot* of simultaneous
users. You will have to code most of the logic on the database side. And
in your case you will not be able to use PowerBuilder to write business logic!
Also I believe that while you can compile web datawindow component as a COM
object and use it in ASP without EAServer you may not be able to use Web
datawindow in PowerDynamo without Jaguar.
I believe in the end Jaguar may actually make your life easier. Perhaps
you can start by using it on a small portion of your application.
Boris Gasin
mailto:[EMAIL PROTECTED]
___
____ _
_____ _
____ _
___
Chief Technology Officer
Dynamic Technology Group, Inc.
http://www.dynamictechgroup.com/
1055 Parsippany Blvd., Suite 501-26
Parsippany, NJ 07054
Phone: 973.402.5600
Fax: 973.402.5620
> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS, ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
