Re^3: High Transaction Data Persistence Requirement across Different Process / Programs

Sorry, I don't think I can help. I've read and re-read your description of the 3 processes, but I cannot make sense of the flow of initiation at all. Hopefully someone with more experience of clustered/cloud-based CC processing will be able to help.

Specifically I don't understand your nomenclature "process A ... make a s call to FCGI process B"? Are you saying that Process A makes an HTML connection to process B?

Nor do I understand "FCGI process C , which is invoked by External systems".

Basically, I'm out of my knowledge zone.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

Comment on Re^3: High Transaction Data Persistence Requirement across Different Process / Programs

Replies are listed 'Best First'.
Re^4: High Transaction Data Persistence Requirement across Different Process / Programs by Anonymous Monk on Jun 29, 2011 at 04:07 UTC
Hi , Let me make a last try to make things clear Process A , Process B and Process C are the 3 Process Process A is a stand alone continuous running perl program which Reads from Linux named queues and process the Message . It picks up the message in the queue , and Makes a LWP call to a FCGI Process This FCGI Process is Process B; FCGI is a persistent CGI process something like mod_perl, when the Process A makes this HTTP call to the FCGI process . This FCGI inturn again makes a HTTP Call gets back a HTTP 200 for it and Updates the Database ; and does a poll on the database tilll.....Basically we are making a Charging request to an asynchronous system FCGI Process C that is running is invoked by the charging system after succesfull processing , this Updates the Database Polling being done earlier ends here as the value is updated in the database; and the value is taken and written into a Linux named queue Hopefully now I am little more clear ?	[reply]

Replies are listed 'Best First'.

Re^4: High Transaction Data Persistence Requirement across Different Process / Programs
by Anonymous Monk on Jun 29, 2011 at 04:07 UTC

Hi , Let me make a last try to make things clear

Process A , Process B and Process C are the 3 Process

Process A is a stand alone continuous running perl program which Reads from Linux named queues and process the Message . It picks up the message in the queue , and Makes a LWP call to a FCGI Process

This FCGI Process is Process B; FCGI is a persistent CGI process something like mod_perl, when the Process A makes this HTTP call to the FCGI process . This FCGI inturn again makes a HTTP Call gets back a HTTP 200 for it and Updates the Database ; and does a poll on the database tilll.....Basically we are making a Charging request to an asynchronous system

FCGI Process C that is running is invoked by the charging system after succesfull processing , this Updates the Database

Polling being done earlier ends here as the value is updated in the database; and the value is taken and written into a Linux named queue

Hopefully now I am little more clear ?

[reply]