core, jp: component handling + client handling refactoring: - SàT can now handle components - plugin have now a "modes" key in PLUGIN_INFO where they declare if they can be used with clients and or components. They default to be client only. - components are really similar to clients, but with some changes in behaviour: * component has "entry point", which is a special plugin with a componentStart method, which is called just after component is connected * trigger end with a different suffixes (e.g. profileConnected vs profileConnectedComponent), so a plugin which manage both clients and components can have different workflow * for clients, only triggers of plugins handling client mode are launched * for components, only triggers of plugins needed in dependencies are launched. They all must handle component mode. * component have a sendHistory attribute (False by default) which can be set to True to allow saving sent messages into history * for convenience, "client" is still used in method even if it can now be a component * a new "component" boolean attribute tells if we have a component or a client * components have to add themselve Message protocol * roster and presence protocols are not added for components * component default port is 5347 (which is Prosody's default port) - asyncCreateProfile has been renamed for profileCreate, both to follow new naming convention and to prepare the transition to fully asynchronous bridge - createProfile has a new "component" attribute. When used to create a component, it must be set to a component entry point - jp: added --component argument to profile/create - disconnect bridge method is now asynchronous, this way frontends can know when disconnection is finished - new PI_* constants for PLUGIN_INFO values (not used everywhere yet) - client/component connection workflow has been moved to their classes instead of being a host methods - host.messageSend is now client.sendMessage, and former client.sendMessage is now client.sendMessageData. - identities are now handled in client.identities list, so it can be updated dynamically by plugins (in the future, frontends should be able to update them too through bridge) - profileConnecting* profileConnected* profileDisconnected* and getHandler now all use client instead of profile

--- a/src/bridge/bridge_constructor/bridge_template.ini	Tue Feb 07 00:15:03 2017 +0100
+++ b/src/bridge/bridge_constructor/bridge_template.ini	Sun Feb 12 17:55:43 2017 +0100
@@ -236,20 +236,23 @@
 doc_return=dictionary with jids as keys and dictionary of asked key as values
  if key doesn't exist for a jid, the resulting dictionary will not have it
 
-[asyncCreateProfile]
+[profileCreate]
 async=
 type=method
 category=core
-sig_in=ss
+sig_in=sss
 sig_out=
 param_1_default=''
+param_2_default=''
 doc=Create a new profile
 doc_param_0=%(doc_profile)s
 doc_param_1=password: password of the profile
+doc_param_2=component: set to component entry point if it is a component, else use empty string
 doc_return=callback is called when profile actually exists in database and memory
 errback is called with error constant as parameter:
  - ConflictError: the profile name already exists
  - CancelError: profile creation canceled
+ - NotFound: component entry point is not available
 
 [asyncDeleteProfile]
 async=
@@ -308,6 +311,7 @@
 doc_param_0=%(doc_profile_key)s
 
 [disconnect]
+async=
 type=method
 category=core
 sig_in=s