messaging

问题 To cut a long story short, I am working on a project where we are rewriting a large web application for all the usual reasons. The main aim of the rewrite is to separate this large single application running on single server into many smaller decoupled applications, which can be run on many servers. Ok here's what I would like: I would like HTTP to be the main transport mechanism. When one application for example the CMS has been updated it will contact the broker via http and say "I've

问题 I was down the pub with a friend of mine yesterday and we started discussing the architecture in use at the company he works at. The conversation basically surrounded the pros/cons of a shared database architecture against a distributed independent application architecture - we couldn't get to a consensus in which case I'd like to hear people's opinions on the pros/cons of both approaches. Basically, the company that he works for has a large architecture with many different applications. Some

问题 I am creating a threaded message system much like gmail and facebook where the inbox lists the most recent threads displaying the subject, the sender's name, and time-stamp of the most recent message. Here's How my tables are set up: users: user_id user_name thread: thread_id title to_id to_keep to_read from_id from_keep date message: message_id thread_id to_id from_id message_text date What I'm doing right now is when a user creates a new message, it creates a new thread in the thread table

问题 I'd like to write some code to monitor the queue size on Websphere 7 MQ. This is the code I've come up with MQEnvironment.hostname = "10.21.1.19"; MQEnvironment.port = 1414; MQEnvironment.channel = "SYSTEM.CDEF.SVRCONN"; MQEnvironment.properties.put(MQC.TRANSPORT_PROPERTY, MQC.TRANSPORT_MQSERIES); MQQueueManager qMgr = new MQQueueManager("MYQMGR"); MQQueue destQueue = qMgr.accessQueue("PUBLISH", MQC.MQOO_INQUIRE); System.out.println(destQueue.getCurrentDepth()); destQueue.close(); qMgr

问题 I'm using Sinch SDK for instant messaging. How to logout user? I have button to logout user, but can't implement that feature in Sinch SDK. Neither their docs or samples describe such feature. 回答1: The sinch client does not have a logout, we consider mobile users to be "online" what you can do if you i.e don't want to receive more push messages is to unregister push data, and if you are not using push, just stop the client. We are using delegated security so if you tell us Joe is logged in

问题 I read slides from this year's UberConf and one of the speakers is making the argument that Spring JMS adds a performance overhead to your message queue system, however I don't see any evidence to support that in the slides. The speaker also makes the case that point-to-point is faster than the traditional "publish-subscribe" method because each message is sent only once instead of being broadcasted to every consumer. I'm wondering if any experienced Java messaging gurus can weigh-in here and

问题 I read slides from this year's UberConf and one of the speakers is making the argument that Spring JMS adds a performance overhead to your message queue system, however I don't see any evidence to support that in the slides. The speaker also makes the case that point-to-point is faster than the traditional "publish-subscribe" method because each message is sent only once instead of being broadcasted to every consumer. I'm wondering if any experienced Java messaging gurus can weigh-in here and

问题 I'm currently doing analysis and design for a new message bus architecture in my company. I have tried MSMQ to do something like this in the past and it works well and was thinking of doing the same thing again for this project but using WCF as the API instead of using the System.Messaging API. Has anyone had experience with MSMQ in WCF? Is it easier to use then the System.Messaging API? What would be some benefits of using WCF over System.Messaging or vice versa? 回答1: IMHO, with so many good

问题 I have difficulties wrapping my head around the concept. I am trying to implement an endpoint that listens on a tcp port for incoming messages in a proprietary format, which would then transform the message and have camel take over the forwarding and routing. Did I understand correctly that that the Producer is responsible for sending messages into the Endpoint and the Consumer receives them from that endpoint? When studying the interfaces I couldn't figure out the message flow between those

问题 As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 8 years ago . We are in need of a distributed architecture messaging system/service bus with the capability of Publish/Subscribe. Does anyone have