Forte web sdk

Question

Hi,
We have just started looking at the Forte Web SDK. We've got the two
examples going on our NT Server running Microsoft's Internet
Information Server. One catch was that we needed to rename the
supplied cgi program to fortecgi.exe (adding .exe extension) on the NT
Server, in the forte code, and in the web pages that call the cgi.
The manual discusses that the web access service objects cannot be
replicated, (since they're tied to a specific IP port), and a
suggested application design is to have a page builder service object
replicated to reduce the chance of a bottleneck. This does not make
much sense to us. Or have we got it wrong?
With this structure they suggest the over-ridden HandleRequest method
can now be something like this
if pageName.isEqual('page1', ignoreCase=true) then
response.assignReponse(pageBuilderService.buildPage1(request));
elseif pageName.isEqual('page2', ignoreCase=true) then]
response.assignReponse(pageBuilderService.buildPage2(request));
else
-- repond with error page
end if;
return reponse;
But even if the pageBuilderService is replicated and a reponse comes
in for page1 a further reponse cannot be handle by this method until
the pageBuilderService returns the completed page1. So what is the
point of replicating the pageBuilderService?
Thanks, Richard
Richard Bentley,
Information Services Section,
University of Canterbury,
Private Bag 4800, Fax: [phone]
Christchurch, Phone: [phone] ext. 7061
NEW ZEALAND. Email: [email protected]
----------------------------------------------------------------

Answer 1

Hi,
We have just started looking at the Forte Web SDK. We've got the two
examples going on our NT Server running Microsoft's Internet
Information Server. One catch was that we needed to rename the
supplied cgi program to fortecgi.exe (adding .exe extension) on the NT
Server, in the forte code, and in the web pages that call the cgi.
The manual discusses that the web access service objects cannot be
replicated, (since they're tied to a specific IP port), and a
suggested application design is to have a page builder service object
replicated to reduce the chance of a bottleneck. This does not make
much sense to us. Or have we got it wrong?
With this structure they suggest the over-ridden HandleRequest method
can now be something like this
if pageName.isEqual('page1', ignoreCase=true) then
response.assignReponse(pageBuilderService.buildPage1(request));
elseif pageName.isEqual('page2', ignoreCase=true) then]
response.assignReponse(pageBuilderService.buildPage2(request));
else
-- repond with error page
end if;
return reponse;
But even if the pageBuilderService is replicated and a reponse comes
in for page1 a further reponse cannot be handle by this method until
the pageBuilderService returns the completed page1. So what is the
point of replicating the pageBuilderService?
Thanks, Richard
Richard Bentley,
Information Services Section,
University of Canterbury,
Private Bag 4800, Fax: [phone]
Christchurch, Phone: [phone] ext. 7061
NEW ZEALAND. Email: [email protected]
----------------------------------------------------------------