On Sat, Aug 22, 2009 at 10:51 AM, gonzus wrote:
>
>
> bsnyder wrote:
>>
>> Request/reply is a versatile style of messaging, but there are no
>> guarantees about the timeliness of the reply. This is where a
>> multi-phased approach would work best when using JMS with HTTP similar to
>> [the workflow
bsnyder wrote:
>
> Request/reply is a versatile style of messaging, but there are no
> guarantees about the timeliness of the reply. This is where a
> multi-phased approach would work best when using JMS with HTTP similar to
> [the workflow approach] you describe below.
>
> [snip]
>
> This [wo
On Fri, Aug 21, 2009 at 5:17 PM, gonzus wrote:
>
> Let's say I have a pure JMS-based application, that implements business logic
> by integrating decoupled components through messaging, with all the
> advantages this entails. These applications are triggered by incoming
> payloads (say, files that
