Re: How to use the SAME transaction in a distributed environment

allond_at_fts-soft.com wrote:

> I know this is a bad idea. Believe me I know :((
> I'll try to explain the nature of my problem a bit more:
>
> What I have are 2 separate *existing* applications. Both are working,
> valid products.
> What I was asked to do is integrate the 2 apps, with minimal impact on
> any of them (and of course we need it now, has to be robust, etc...)
>
> Application 'A' is GUI-oriented, and application 'B' is more of a
> back-office nature.
> What I want to achieve is that when 'A' creates a new entity, it will
> call 'B' to create the needed entity/ies, and then one commit will be
> done - to ensure that either both 'A' and 'B' succeded, or nobody did.
> Hope this clarifies the problem a bit...
>
> Thanks,
>
> Allon.

I think the best solution, well other than firing the person in management that purchased the original software without considering integration issues, would be to write a third application that interacts with A and B.

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace 'x' with 'u' to respond)