Change Details

To accept notifications in native format, plan is to have one gate. As this is different to the current model "one service, one gate", we need to stop to hardcode SERVICE_NAME as a class constant and allow each gate to determine the service name. Ref T979

To accept notifications in native format, plan is to have one gate. This gate will so receive payloads from different services, and this service will be available in the payload (in the service property). Currently, service name is hardcoded as a SERVICE_NAME constant. Instead, each gate will provide a custom getServiceName() method. Gates for one service (ie all our current gates) now have such methods to return the same string than the former SERVICE_NAME value. More complex gates will customize this logic. Ref T979

To accept notifications in native format, plan is to have one gate. This gate will so receive payloads from different services, and this service will be available in the payload (in the service property). As this is different to the cCurrent model "one servicely, one gate",service name is hardcoded as a SERVICE_NAME constant. we need to stop to hardcode SERVICE_NAME as a class constant andInstead, each gate will provide a custom getServiceName() method. Gates for one service (ie all our current gates) now have such methods allow each gate to determine the service nameto return the same string than the former SERVICE_NAME value. More complex gates will customize this logic. Ref T979