RE: JMS implementation source code

From: Thomas Mercer-Hursh, Ph.D.

Date: 2 Nov 2005

At 06:09 11/2/2005, David E. Cleary wrote:
>... In fact, we put quite a bit of
>resources in adding support for fault tolerant connections and client
>persistence for the 10.1A release as this was something our customers
>have been asking for for years.
>
>I don't know how much value one would get out of having access to the
>4GL code. All it is is temptable manipulation and AppServer calls.

Providing a high quality component that supports advanced features of 
Sonic is a nice thing to do for your customers, however, by making it 
.r code only and tying it strongly to Sonic, you have simultaneously 
failed to give something to those customers who have a reason not to 
use Sonic, but do have a need for messaging.  Sonic is price 
positioned as an integration technology.  Some of us would like to 
use a MOM product to provide within application messaging, in part 
because PSC has thus far failed to provide pub/sub outside a single 
session.  I.e., this is pure and simple vendor lock-in, not the 
maximal service you could provide to your customers.



=========================================================================
Thomas Mercer-Hursh, Ph.D.               email: 8b4a52fe-9ac3-7dbb-de11-b2010483b62c
Computing Integrity, Inc.                voice: 510-233-5400
60 Belvedere Avenue                        fax: 510-233-5446
Point Richmond, CA 94801-4023              url: http://www.cintegrity.com
=========================================================================
    Consulting in Architecture-Driven Modernization and Transformation