Why are there two separate JMS API domains, point-to-point and publish/subscribe, instead of just one?
Even though there are many similarities, providing separate domains still seems to be important. It means that vendors aren’t forced to support facilities out of their domain and that client code can be a bit more portable because products more fully support a domain (as opposed to supporting less defined subsets of a merged domain).
Related Questions
- Does the specification require that all JMS implementations provide both point-to-point and publish/subscribe messaging?
- Why are there two separate JMS API domains, point-to-point and publish/subscribe, instead of just one?
- How can the remote publish/subscribe use case work? Aren JMS implementations incompatible?
