| Author |
Message
|
| eputsato |
 Posted: Thu Apr 16, 2009 2:00 am Post subject: |
 |
|
Novice
Joined: 14 Apr 2009
Posts: 20
|
| WMBDEV1 wrote: |
| mqjeff wrote: |
The more you reject these solutions, the more you work yourself into a corner where nothing sensible can be done. |
and heres my latest wacky suggestion....
Create a new subscription point on the topic and have your publisher send one in ten (or whatever) messages to it. You will have to create some sort of state on the flow but I did say it was wacky!
The slow subscriber will then subscribe to this topic and sub point. |
Could you pleaase clarify - I haven't managed to get your idea |
|
| Back to top |
|
 |
| WMBDEV1 |
| Posted: Thu Apr 16, 2009 2:07 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
So......
You currently have a topic where all messages currently get published to and all your subscribers get their feed from.
In your flow you could create another publish node using the same topic as before but with a subscription point (set on the pub node) of something like "SLOWAPPS".
You could then write some logic to always propagate to the default publish and propagate to the SLOWAPPS point for one in every ten messages.
When you create the subscription for the slow app you also specify the sub point of "SLOWAPPS". It will only receive one in ten messages then.
Any better? |
|
| Back to top |
|
|
| eputsato |
| Posted: Thu Apr 16, 2009 2:16 am Post subject: |
|
|
Novice
Joined: 14 Apr 2009
Posts: 20
|
| WMBDEV1 wrote: |
So......
You currently have a topic where all messages currently get published to and all your subscribers get their feed from.
In your flow you could create another publish node using the same topic as before but with a subscription point (set on the pub node) of something like "SLOWAPPS".
You could then write some logic to always propagate to the default publish and propagate to the SLOWAPPS point for one in every ten messages.
When you create the subscription for the slow app you also specify the sub point of "SLOWAPPS". It will only receive one in ten messages then.
Any better? |
Thank you! This is what can be done. But one more question. Whre to propagate changes from queue to the other? From fast subscriber or from server side? |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Thu Apr 16, 2009 2:30 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| eputsato wrote: |
But one more question. Whre to propagate changes from queue to the other? From fast subscriber or from server side? |
I'm not sure I understand....
The changes are always propagated from the publisher (broker).
The subscribers have no knolwedge of each other. |
|
| Back to top |
|
|
| eputsato |
| Posted: Thu Apr 16, 2009 2:31 am Post subject: |
|
|
Novice
Joined: 14 Apr 2009
Posts: 20
|
| Ah, you meant to add the other topic? And to publish there only one of 10 messages? |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Thu Apr 16, 2009 2:41 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| Its not a new topic, the same topic is used but you add a subscription point and publish one in ten messages to this point on the topic. |
|
| Back to top |
|
|
| eputsato |
| Posted: Thu Apr 16, 2009 2:44 am Post subject: |
|
|
Novice
Joined: 14 Apr 2009
Posts: 20
|
| What is a subscription point. I mean how to publish to it? |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Thu Apr 16, 2009 2:47 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
As previously stated:
| Quote: |
| In your flow you could create another publish node using the same topic as before but with a subscription point (set on the pub node) |
Look at the properties of the node. |
|
| Back to top |
|
|
|
|
