I'm going with A, B, and D. Using a queue processor (D) to pass updated attributes sounds like a slick way to keep things synced up. Can't go wrong with the classics, you know?
Hah, using SQL to exchange data in a web mashup? That's like trying to open a jar of pickles with a sledgehammer. A, B, and D are clearly the way to go here.
I like the idea of using an action object as a script (A) - that gives me more control over the data exchange. And the data-pega-event-onpagedata attribute (E) sounds interesting, I'll have to look into that one.
A, B, and D seem like the most straightforward options to exchange data. Using an SQL call to exchange data (C) seems a bit risky and could be overkill for a simple web mashup.
Salome
2 days agoDeonna
8 days agoTandra
13 days agoTomoko
14 days agoGaston
21 days agoNieves
24 days agoVeronique
26 days ago