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

If you don't need the data to be safe, you can look at something like memcached. Perl has modules for accessing memcached.

If you can tie all three processes onto one machine, maybe it is enough to pipe the data from the first process to the next process and so on? Or does the first process need (write) access to the session ID after it has given the ID to the second process?

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

Replies are listed 'Best First'.
Re^2: High Transaction Data Persistence Requirement across Different Process / Programs by Anonymous Monk on Jun 28, 2011 at 12:45 UTC
Hi All 3 Process are on one Machine itself I need to run a Memcache server for the same ? Shall look into the URLS Thanks	[reply]
Re^2: High Transaction Data Persistence Requirement across Different Process / Programs by Anonymous Monk on Jun 28, 2011 at 13:29 UTC
Hi, How stable is memcache ? The data we are dealing with is related to charging , so the data is critical	[reply]
Re^3: High Transaction Data Persistence Requirement across Different Process / Programs by Corion (Patriarch) on Jun 28, 2011 at 16:01 UTC
`memcached` is not a persistent queue solution. If the memcached process goes down, all information in it is lost.	[reply] [d/l]
Re^4: High Transaction Data Persistence Requirement across Different Process / Programs by Anonymous Monk on Jun 29, 2011 at 04:13 UTC
Oh !! Ok , what would be another alternate ?	[reply]
Re^5: High Transaction Data Persistence Requirement across Different Process / Programs by Corion (Patriarch) on Jun 29, 2011 at 06:38 UTC