messaging | 易学教程

Microsoft.ServiceBus.Messaging vs Microsoft.Azure.ServiceBus

阅读更多关于 Microsoft.ServiceBus.Messaging vs Microsoft.Azure.ServiceBus

问题 MS has recently introduced the Microsoft.Azure.ServiceBus namespace. https://github.com/Azure/azure-service-bus/blob/master/samples/readme.md It is geared for the new .net standard framework (as if MS doesn't have enough semi-redundant code bases) My question is, how much better could it be in terms of performance? I can say with confidence, that the Microsoft.ServiceBus.Messaging leaves lots to be desired, in particular when it comes to persistent receiving. A very useful feature of the

Websphere 7 MQueue: how to access queue depth from Java?

阅读更多关于 Websphere 7 MQueue: how to access queue depth from Java?

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.disconnect(); How do I know what the "Channel" is? How do I know what the queue manager name is that I pass

Sinch SDK - How to logout user?

阅读更多关于 Sinch SDK - How to logout user?

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. 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 with you key and secret we trust that you have verified the user. 来源： https://stackoverflow.com/questions

Messaging system database schema

阅读更多关于 Messaging system database schema

问题 I'm trying to implement a messaging system in PHP and MySQL but I'm having some trouble deciding on how I should do the tables and queries. What would be the best approach for a system that allows for multiple participants? I'm thinking I'd probably need 3 tables (aside from an users table). Something like Conversation ------------ id Messages -------- id conversation_id from_id subject message from_timestamp Participants ------------ conversation_id user_id last_read_timestamp The way it is

How to use Android App as a “Producing client” for Kafka?

阅读更多关于 How to use Android App as a “Producing client” for Kafka?

Is it possible / does it make sense to use an Android app as a "Producing client" for Apache Kafka? Let's say my Android App need to capture and analyse reaction time data. Goal is to collect all data and show the average reaction time in real-time in the App. The alternative is having an app server of some kind as an intermediary that accepts messages from the android app and posts them to Kafka, rather than having the app be a Kafka Producer on its own. Even if it's possible, in my opinion it has some disadvantages. In general I like clients to be as simple as possible to avoid maintenance

Proper way of using MVVM Light Messenger

阅读更多关于 Proper way of using MVVM Light Messenger

问题 What is the proper way to use Messenger class ? I know it can be used for ViewModels/Views communications, but is it a good approach to use it in for a technical/business service layer ? For example, a logging/navigation service registers for some messages in the constructors and is aware when these messages occurs in the app. The sender (ViewModel ou Service) does not reference the service interface but only messenger for sending messages. Here is a sample service : using System; using

Private messaging in Django

阅读更多关于 Private messaging in Django

问题 I'm looking for a preexisting Django app providing user to user private messaging. I've seen django-pm and django-messages, neither of which appear to be in particularly active development. Is there really nothing out there? 回答1: I know this question is a bit old, but this looks promising django-postman. I'm about to try it out for a project I'm working on. I found it here: http://djangopackages.com/grids/g/messaging/ If you haven't seen it before Django Packages is a great site for finding

Passing message from background.js to popup.js

阅读更多关于 Passing message from background.js to popup.js

I'm trying to implement my own chrome extension on which, on a certain event, create a browser notification and fills the popup with data calculated in background.js Here is mymanifest file : { "name": "Dummy name", "description": "Description", "manifest_version": 2, "version": "1.1.3", "icons": { "16": "icon_16.png", "48": "icon_48.png", "128": "icon_128.png", "256": "icon_256.png" }, "browser_action": { "default_icon": "icon_48.png", "default_title": "Test", "default_popup": "popup.html" }, "permissions": ["background","webRequest","webRequestBlocking","webNavigation","tabs","notifications"

What kind of technologies are available for sending text messages? [closed]

阅读更多关于 What kind of technologies are available for sending text messages? [closed]

问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 11 months ago . I'm looking into sending regular automated text-messages to a list of subscribed users. Having played with Windows Mobile devices, I could easily implement this using the compact .Net framework + a device hooked up to usb and send the messages through this. I would like to explore other solutions like having a

High Performance JMS Messaging

阅读更多关于 High Performance JMS Messaging

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 clarify a few technicalities: Is there actually a performance overhead incurred by using Spring JMS