New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

perdp.* feature #15

Closed
monnand opened this Issue Apr 19, 2013 · 1 comment

Comments

Projects
None yet
1 participant
@monnand
Member

monnand commented Apr 19, 2013

When push to a certain user, some field needs to be vary on different delivery point.

perdp.* features are a kind of parameter containing a list of values, for each delivery point, it will randomly received one of the value in the list and there is no duplication if the list size is less than the number of delivery points.

Example:

User monnand under service news has 3 devices, then if we execute the following command:

curl http://127.0.0.1:9898/push -d service=news -d subscriber=monnand -d perdp.mid="1,2,3" -d msg="News!"

Then 3 of the devices under monnand will received notifications with a parameter named perdp.mid whose value will be 1 or 2 or 3 respectively. Since there are 3 devices and 3 values under perdp.mid, there will be no two devices receiving perdp.mid parameter with same value.

This feature is specifically useful for uniqush-conn to send the message id.

@ghost ghost assigned monnand Apr 19, 2013

monnand added a commit that referenced this issue Apr 19, 2013

@monnand

This comment has been minimized.

Show comment
Hide comment
@monnand

monnand Apr 19, 2013

Member

Fixed. This should be a hidden feature, only used by uniqush-conn. (at least in 1.4.3)

Member

monnand commented Apr 19, 2013

Fixed. This should be a hidden feature, only used by uniqush-conn. (at least in 1.4.3)

@monnand monnand closed this Apr 19, 2013

monnand added a commit that referenced this issue Apr 19, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment