[Openroad-users] App Server processing

[Fabian Anderson]

Hi Martin,

            If you are working with a Transforged application, you do not need to split the code into two parts.  If you do not have a Transforged application, simply make sure that ALL callframe/openframe/gotoframe statements a handled by a centralized "frame control object" (which can subsequently suppress frame invocations and recall other user interactions).

 

            We have tested this on our Fintechnix (BackOffice) application and it is working perfectly.  All that was required was an include script at the point were the code would have been split.

 

Cheers,

Fabian Anderson,

Systems Analyst / Programmer

Fintechnix Pty Ltd.

 

P.S.  You should remember how all Fintechnix frames were called from within an .Invoke( ...) method.  

 

 

________________________________

From: openroad-users-bounces at peerlessit.com [mailto:openroad-users-bounces at peerlessit.com] On Behalf Of Martin Pomej
Sent: Thursday, 23 November 2006 10:37
To: 'Kim Ginnerup'; OpenROAD Users
Subject: Re: [Openroad-users] App Server processing

 

Hi Kim,

 

Thanks for your reply. I'm happy that what I thought was correct, is correct, but I'm unhappy that I am correct 8-)

 

Main issue is that the popup's appear in a number of locations, so breaking it down to two or more calls is going to be painful.

 

Regards, 
Martin. 

 

PS

Does anybody have access to bulk supplies of aspirin?

 

________________________________

From: Kim Ginnerup [mailto:kgi at bording.dk] 
Sent: Thursday, 23 November 2006 02:43
To: martin.pomej at myworkplace.com.au; International OpenROAD Users
Subject: SV: [Openroad-users] App Server processing

Hi Martin,

 

There is only one way you can accomplish that.

Split the server call into two calls.

You are already using a stateful server, so keeping the state between the two calls shouldn't that big a deal.

 

On thing you will need to handle is the situation that the user bails out between the first and the second call.

But that is something you will need to handle anyway with a stateful server.

Hopefully you popup is not in the middle of a transaction.  ;-)

 

Kim

________________________________

Fra: openroad-users-bounces at peerlessit.com [mailto:openroad-users-bounces at peerlessit.com] På vegne af Martin Pomej
Sendt: 22. november 2006 16:22
Til: OpenROAD Users
Emne: [Openroad-users] App Server processing

 

Hello OpenROAD legends,

 

We have a tough situation involving App Server and some heavy processing and I wanted to ask if anyone had encountered anything similar and how they handled it.

 

Scenario

- existing app converted to eClient / App Server

- heavy processing moved to App Server due to the massive amount of data involved

- depending on variables, certain processing will occur and then the user will be prompted for a response (this is how the fat client currently works)

 

Problem

- the prompting involves a frame popping up and requesting information

- the information gathered in the prompting cant be requested prior to calling App Server

 

Ideal Solution

- make a call to App Server and when a certain point in the App Server processing is reached, halt what's happening and return control back to eClient

- prompt the user for the required information

- pass information and control back to App Server and continue on with processing from the point where App Server was halted

 

My question is can App Server be dealt with in this way? If so how?

(With my limited App Server experience I cant see this working, but I want to ask to be 100%)

 

If anyone has dealt with a similar scenario whereby processing on App Server was halted, control returned to eClient and then control again returned to App Server, would you mind sharing the way you went about it.

I've almost lost the 2 strands of hair I have left just thinking about handling this, and surely my hair is worth saving 8-P.

 

Regards, 
Martin Pomej 
MyWorkplace Solutions Pty Ltd 
Ph:     1300 733 731 
Mob:    0414 230 845 
Em:     martin.pomej at myworkplace.com.au 
Making Service our Priority 
www.myworkplace.com.au <http://www.myworkplace.com.au/>  

 


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________


Specialist providers of back and front office systems for the financial services industry.
Featuring:  Fintechnix(r)
Disclaimer: 
Notice: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it.
Any views expressed in this message are those of the individual sender,except where the sender specifically states them to be the views of Fintechnix Pty Ltd.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://peerlessit.com/pipermail/openroad-users/attachments/20061123/5e9acc21/attachment.html