Welcome to MSDN Blogs Sign in | Join | Help

Event name suggestions?

So, we are trying to figure out a good name for an event for the following:

The mechanism by which you access published capabilities and objects from a person near you is by calling the PeerCollabRefreshEndpointData() API. This API effectively refreshes the local cache with whatever data is being published by the endpoint. Since this is a network operation, it is asynchronous, and has an event for when the operation completes. We are trying to figure out a good name for this operation.

Any thoughts, on what sounds like a good name? Each event is associated with a structure containing the data that was returned. Please give suggestions!

PEER_EVENT_ENDPOINT_DATA_REFRESHED

PEER_EVENT_ENDPOINT_DATA_CHANGED

PEER_EVENT_ENDPOINT_DATA_AVAILABLE

Any other ideas?

Published Friday, October 07, 2005 10:55 PM by ravirao

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# re: Event name suggestions?

Clearly AVAILABLE or REFRESHED (I lean towards AVAILABLE). CHANGED is misleading since I guess the data could still be the same as before, if the cache happened to be up to date.
Saturday, October 08, 2005 2:17 AM by anon

# re: Event name suggestions?

This must be a win32 API. The names look like a mess and do not follow guidelines.

When MS will finally start supporting .NET and stop doing new win32 APIs. Windows After Vista? Let's hope so.
Saturday, October 08, 2005 8:57 AM by zzz

# re: Event name suggestions?

Personally, I like "refreshed".

PEER_EVENT_ENDPOINT_DATA_LOADED
PEER_EVENT_ENDPOINT_DATA_CACHED

Saturday, October 08, 2005 9:21 AM by James

# re: Event name suggestions?

The API is PeerCollabRefreshEndpointData so the event should have the matching name REFRESHED.

Question though: after refreshing the local cache are changes then kept up-to-date or do you need to keep calling this API periodically to see further changes?

If the local cache is updated automatically, then Refresh gives a wrong meaning. Subscribe and SUBSCRIBED would be more appropriate. However, if you need to call the API periodically, then Refresh is fine.
Saturday, October 08, 2005 10:19 AM by Adrian Moore

# re: Event name suggestions?

This is just awesome. Thanks for the feedback.
Adrian, to answer your question, the API needs to be called periodically (depending on how frequently the application wants to check for updates). I think we will go with REFRESHED, since most of you either like it, or are ok with it.

zzz, to answer your question, I don't have a timeline when Microsoft will have .net APIs. However, Adrian Moore (http://mooresmind.blogspot.com) is building managed wrappers for these APIs, and you may be able to use those.
Saturday, October 08, 2005 1:42 PM by ravirao

# re: Event name suggestions?

need a good name for a event which is going to happen within a process. but has to be a fgrreace full with the touch of sucess

Thursday, August 16, 2007 6:00 AM by event name

# re: eventand promotion name

we r going to start event and promotion managment compant are target market whould be rural area so pleas suggest me any good name

Wednesday, March 18, 2009 6:38 AM by for rural market

# Ravi Rao s Blog Event name suggestions | Paid Surveys

Leave a Comment

(required) 
required 
(required) 

  
Enter Code Here: Required
 
Page view tracker