Anne, On Jun 30, 2006, at 4:31 AM, Anne Thomas Manes wrote:
> But JMS is not a transport -- it's a programming API. > Hmm, maybe this gets it across: *** HTTP is a programming API *** Jan > (It's just that each JMS implementation comes with a proprietary > transport.) > > Anne > > > On 6/29/06, Stanley Stanev <[EMAIL PROTECTED]> wrote: > you can always abstract the transport even if you use the languages > you just described just to be able to change transports without any > problems, so you do not care if it is JMS or not > > you introduce an abstraction layer that decouples you from the > transpiort > > you still want to go SOAP, no matter what the transport is > > thanks, > Stanley Stanev > > > > Anne Thomas Manes wrote: >> JMS isn't much use if you're building applications in C#, VB, >> COBOL, Perl, PHP, Python, Ruby, JavaScript, etc. >> >> Language dependency is an anathma to SOA. >> >> Anne >> >> >> On 6/28/06, patrickdlogan <[EMAIL PROTECTED] > wrote: >> > the JMS requirement was only there because the initial proponents >> > happened to be JMS vendors. >> >> There are reasons for this that should be considered. >> >> I know it is an API and not a priori "interoperable" (in all the >> dimensions of that term), but many implementations are interoperable >> in various ways. And it is fairly simple yet expressive. >> >> I would suggest there are a number of vendors of JMS due to its >> simplicity (it can be implemented and used without a ton of effort) >> and expressiveness (it can be used successfully, widely). For all of >> these reasons it seems something like JMS should be the core of an >> ESB. >> >> -Patrick >> >> > > > -- > ---------------------------------------- > Stanimir Stanev (Stanley) > Senior Java Developer > www.stanev.com ---------------------------------------- > > > > ------------------------ Yahoo! Groups Sponsor --------------------~--> Check out the new improvements in Yahoo! Groups email. http://us.click.yahoo.com/6pRQfA/fOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
