I'm trying to use NSServerNotificationCenter, but it's not working. That is, 
I'm not actually getting any notifications.

When I set up the node on the server, I issue the commands as documented:

$ notificationconf usessl me.com
$ notificationconf setpass me.com myusername
Enter password: 
$ notificationconf createnode me.com mynotification myusername
Enter password: 
2010-05-07 00:12:24.787 notificationconf[27584:903] created XMPP session
2010-05-07 00:12:24.791 notificationconf[27584:903] Connecting to me.com:5222 
with user [email protected]/TestPubsub, security = 2 ...

I'm worried about a couple things I see there. First, the user is not 
myusername, and it's going to "TestPubsub," implying a test setup.

When I register in my app for the notification, I always get prompted to give 
permission to access the keychain (despite clicking "Always Allow").

I also see this in Console.app when I try to send a notification:

5/7/10 00:18:01         AOSNotification[189]    [AOSNotification] Attempt to 
publish to without active session established for JID [email protected]

When my notification code (a simple test app separate from the one receiving 
the notification) attempts to post a notification, it also prompts for keychain 
access.

- Am I doing something wrong? The notification name I'm subscribing to and 
posting to matches the node name I provided above.

- How can I send notifications to multiple users? I presume they must each 
issue the same notificationconf commands, which is a terrible user experience. 
But how does the server keep node names from users from colliding? Surely I'm 
not expected to give my users my login credentials?

Any help would be much appreciated.

-- 
Rick

_______________________________________________

Cocoa-dev mailing list ([email protected])

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to