• Post Reply Bookmark Topic Watch Topic
  • New Topic

Enterprise Integration using messaging - comment requested  RSS feed

P Das
Ranch Hand
Posts: 123
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
From SCEA perspective, I request comment on the following.

A prescribed book "Enterprise Integration Patterns Designing, Building, and Deploying Messaging Solutions" says the following:

1) "TCP/IP is a connection-oriented protocol" p.13; also carried over at other places, e.g. "TCP/IP connections" p. 15. -- Did the author(s) mean just TCP, which appears from their mentioning socket in nearby places? I had written to one of the authors asking the same question that has not been responded.

2) In section titled "Reliable Communications", p. xxxv. they say, "The reason messaging is more reliable than RPC ...", and went on to talk about Guaranteed Delivery. -- Is messaging more reliable than RPC or blocking sessions?

3) Overall, it seems that they use "message" to implicitly include Message Oriented Middleware. This appears to be different from the usage in Object Oriented design, since in the later parlance message means invoking a method of an object by another object. -- Which one should be acceptable in the context of SCEA?

It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!