Thunderforce UUIDs: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 7: | Line 7: | ||
*{591f1656-2808-11dc-8314-0800200c9a69}: nsISalesforcePartner | *{591f1656-2808-11dc-8314-0800200c9a69}: nsISalesforcePartner | ||
*{591f1656-2808-11dc-8314-0800200c9a70}: nsISalesforceBidirectionalPartner | *{591f1656-2808-11dc-8314-0800200c9a70}: nsISalesforceBidirectionalPartner | ||
*{591f1656-2808-11dc-8314-0800200c9a71}: nsISalesforceBidirectionalPartnerListener |
Revision as of 09:36, 26 August 2007
The following UUIDs are in use within Thunderforce. When you need a new UUID, please claim it here first and then use it. To make things simpler, please increment the UUID by one for each new UUID.
UUIDs in use
- {591f1656-2808-11dc-8314-0800200c9a66}: nsThunderforceProtocolInfo
- {591f1656-2808-11dc-8314-0800200c9a67}: nsThunderforceServer
- {591f1656-2808-11dc-8314-0800200c9a68}: nsThunderforceTestCommandLine
- {591f1656-2808-11dc-8314-0800200c9a69}: nsISalesforcePartner
- {591f1656-2808-11dc-8314-0800200c9a70}: nsISalesforceBidirectionalPartner
- {591f1656-2808-11dc-8314-0800200c9a71}: nsISalesforceBidirectionalPartnerListener