Hi, Delving more into the service oriented design I have come accross as issue...
I have two services. Service A - is a message consumer off of a messaging infrustructure. Service B - is a Queue I have a application that needs to use Service A to read messages off of the messaging bus and fill up the Queue of service B with certain types of those messages. Now, keeping in mind some of the best practices of service oriented design of ensuring each service does one thing and does it well, I don't want Service A to have to know about Service B, as I'd like to use Service A with other non-Queue based applications. Any recommendations on how to keep a clean design here implementing this ? appreicate commets. korosh --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]