{"payload":{"header_redesign_enabled":false,"results":[{"body":"Objective C // Import Headers # import < DetectStreamKit/DetectStreamKit.h > // Create an instance of DetectStreamManager DetectStreamManager *detectstreammgr = [DetectStreamManager new ]; // Detect any streams NSDictionary * d = [_detectstreammgr detectStream ]; // Check if we are playing anything if (d[ @\" result \" == [ NSNull null ]) { // Nothing is playing NSLog ( @\" Nothing Playing! \" );\n} else { // Populate Data NSString * title = [d objectForKey @\" title \" ]; NSNumber * episode = [d objectForKey @\" episode \" ]; NSNumber * season = [d objectForKey @\" season \" ]; NSString * site = [d objectForKey @\" site \" ]; // Print the stream information NSLog ( @\" %@ - %d - %d - %@ \" , title, [episode intValue ], [season intValue ], site);\n}","filename":"Usage.md","format":"markdown","hl_body":"Objective C // Import Headers # import &lt; DetectStreamKit/DetectStreamKit.h &gt; // Create an instance of DetectStreamManager DetectStreamManager *detectstreammgr = [DetectStreamManager new ]; // Detect ...","hl_title":"<em>Usage</em>","id":"253a807540a78e7c533fd15e669278c41028866f","path":"Usage.md","public":true,"repo":{"repository":{"id":25560969,"name":"detectstream","owner_id":10914575,"owner_login":"Atelier-Shiori","updated_at":"2023-08-07T18:26:26.791Z","has_issues":true}},"repo_id":25560969,"title":"Usage","updated_at":"2018-07-31T16:44:14.000-04:00"},{"body":"","filename":"usage.md","format":"markdown","hl_body":"","hl_title":"<em>usage</em>","id":"f8dade3faad97431c967e42735eb333064e4b40d","path":"usage.md","public":true,"repo":{"repository":{"id":33309650,"name":"cnova-sdk","owner_id":126154,"owner_login":"gpupo","updated_at":"2019-03-02T13:58:28.991Z","has_issues":true}},"repo_id":33309650,"title":"usage","updated_at":"2016-07-07T10:18:10.000-03:00"},{"body":"USB HID devices and their components can be given a Usage code.  The Usage code\nis an optional suggestion to the application on what the control is to be used for. A usage code is broken up into two parts: the Usage Page and the Usage.  \nBoth are 16-bit numbers (0-65535).  Any values can be used, but there are a\nset of defined values. The Usage Page is used to group usages.   A set of Usage Pages has been\ndefined by the USB group.  These are listed below... GENERIC_DESKTOP_CONTROLS 0x01 SIMULATION_CONTROLS 0x02 VR_CONTROLS 0x03 SPORT_CONTROLS 0x04 GAME_CONTROLS 0x05 GENERIC_DEVICE_CONTROLS 0x06 KEYBOARD_KEYPAD 0x07 LEDS 0x08 BUTTON 0x09 ORDINAL 0x0A TELEPHONY 0x0B CONSUMER 0x0C DIGITIZER 0x0D PID_PAGE 0x0F UNICODE 0x10 ALPHANUMERIC_DISPLAY 0x14 MEDICAL_INSTRUMENTS 0x40 MONITOR_PAGES 0x83 POWER_PAGES 0x87 BAR_CODE_SCANNER_PAGE 0x8C SCALE_PAGE 0x8D MAGNETIC_STRIPE_READING_DEVICES 0x8E CAMERA_CONTROL_PAGE 0x90 ARCADE_PAGE 0x91 VENDOR_DEFINED 0xFF00 Each Usage Page has a collection of Usages.   For example, these are Usages for\nthe Usage Page GENERIC_DESKTOP_CONTROLS. POINTER 0x01 MOUSE 0x02 JOYSTICK 0x04 GAME PAD 0x05 KEYBOARD 0x06 KEYPAD 0x07 X 0x30 Y 0x31 Z 0x32 RX 0x33 RY 0x34 RZ 0x35 SLIDER 0x36 DIAL 0x37 WHEEL 0x38 HATSWITCH 0x39 START 0x3D SELECT 0x3E DPAD_UP 0x90 DPAD_DOWN 0x91 DPAD_RIGHT 0x92 DPAD_LEFT 0x93 Generally, it is not important what the Usage Page and Usage are, however\nthere are some exceptions... LCD display modules must have a Usage of\nALPHANUMERIC_DISPLAY:ALPHANUMERIC_DISPLAY otherwise it will not be\nidentified as a display device.   Generic HID will not let this be\nchanged. A directional switch/hat switch must be called GENERIC_DESKTOP_CONTROLS:HATSWITCH\notherwise the values will not be reinterpreted as a directional angle. To get Windows and other operating systems to recognise the device as a\njoystick or game pad, it must be called GENERIC_DESKTOP_CONTROLS:JOYSTICK or GENERIC_DESKTOP_CONTROLS:GAMEPAD.  \nWindows will also typically want the usage of an axis set X, Y, Z, etc. Avoid using GENERIC_DESKTOP_CONTROLS:MOUSE or GENERIC_DESKTOP_CONTROLS:POINTER\nas the usage for a device.   The operating system will take control of\nthe device and interpret actions as mouse moves and button presses. The property field for the Usage is displayed as the Usage Page and the\nUsage.   These are two drop down lists that contain the standard Usage Pages\nand Usages as shown below. It is not necessary to use one of the predefined values.","filename":"usages.md","format":"markdown","hl_body":"USB HID devices and their components can be given a <em>Usage</em> code.  The <em>Usage</em> code\nis an optional suggestion to the application on what the control is to be used for. A <em>usage</em> code is broken up into two ...","hl_title":"<em>usages</em>","id":"2d33df074908aee59f64a838f43e0e47b24f9166","path":"usages.md","public":true,"repo":{"repository":{"id":34788505,"name":"GenericHID","owner_id":1462773,"owner_login":"ftkalcevic","updated_at":"2019-10-23T10:01:18.152Z","has_issues":true}},"repo_id":34788505,"title":"usages","updated_at":"2019-10-06T08:34:04.000+11:00"},{"body":"Requirements These are the requirements to be able to use this utility in your code: Having installed log4db2 in the database. Change/activate the SQL access level in the stored procedures or functions MODIFIES SQL DATA . The user used to execute your routines should be able to execute the log4db2 routines. Usage in the source code NOTE : Each time you call log4db2 make sure the message you are passing does not contain sensitive information. The security for the business tables could not be the same for the logger table. Because of this reason, information in the LOG table could be exposed. To use log4db2 from your code, you need to know two stored procedures: GET_LOGGER . LOG Also, instead of using the LOG stored procedure, you can use the macros: DEBUG . INFO . WARN . ERROR . FATAL . The previously stored procedures will be explained in detail in the following sections. The table below shows the database objects used when developing an application. All the routines (stored procedures and functions) are under LOGGER module, which is under the LOGGER_x schema (where x is the log4db2 version). Object name Type Description DEBUG Proc Macro to log messages in 'DEBUG'-5 level. ERROR Proc Macro to log messages in 'ERROR'-2 level. FATAL Proc Macro to log messages in 'FATAL'-1 level. GET_LOGGER Proc Registers the name of a logger and returns the ID for that logger. GET_LOGGER_NAME Func Retrieves the logger name for a given logger ID. INFO Proc Macro to log messages in 'INFO'-4 level. LOG Proc Writes the log message to the appenders. This function formats the message according to the layout. LOG Tabl This table contains the log messages. This table is in the LOGDATA schema, but it has a public alias that allows to access the table without the schema. WARN Proc Macro to log messages in 'WARN'-3 level. GET_LOGGER Procedure First, a logger could be considered like a stored procedure or function (a routine), or a set of them that generate logs. The GET_LOGGER stored procedure receives a name and returns the ID of that name in the internal hierarchy of the utility. The hierarchy is defined by dots, starting from the lower level and ascending to the last son. Root is the ancestry of all loggers. For example the name foo.bar.tata has the following hierarchy: ROOT\n+--foo\n   +--bar\n      +--tata Another example could be foo.toto and its hierarchy is: ROOT\n+--foo\n   +--toto The two examples in the same hierarchy give: ROOT\n+--foo\n   +--bar\n   |  +--tata\n   +--toto As you can see toto and bar are siblings, with a common parent foo . ROOT is always present because is the root logger. It is important to indicate that YOU define the hierarchy. You give names separated by dots to indicate different 'modules', 'packages', or whatever you consider appropriate. Advice is to use the same hierarchy of the database (at least to start with this approach): schema.module.storedProcedure and schema.module.function . The returned number is generated by the utility, and it allows to determine which logger generated a log. This is not important, and you do not have to deal with this number; you just have to generate it ( GET_LOGGER ) and pass it when logging ( LOG ). It is very important to create your routines with the flag MODIFIES SQL where log4db2 is going to be used directly or indirectly. If you do not do that, when issuing the first call, an error message will be raised. Please check this article . Note: The ROOT word is reserved only for root logger. Therefore, no other logger can have this name nor a part of a hierarchy. Example Let's consider two stored procedures called 'pitagoras' and 'fibonacci' that realize mathematical computations. Both of them are in the same schema 'maths'. maths.pitagoras\nmaths.fibonacci You pass the complete name of each stored procedure to the logger.get_logger stored procedure. Each of them will have a different logger id because they were registered with a different hierarchy. CREATE PROCEDURE MATHS.PITAGORAS (...)\nBEGIN\n  DECLARE LOGGER_ID SMALLINT;\n  LOGGER.GET_LOGGER('maths.pitagoras', LOGGER_ID);\n  ...\nEND@\n\nCREATE PROCEDURE MATHS.FIBONACCI (...)\nBEGIN\n  DECLARE LOGGER_ID SMALLINT;\n  LOGGER.GET_LOGGER('maths.fibonacci', LOGGER_ID);\n  ...\nEND@ However, you could decide that you are going to register them only 'maths', and you will have the same logger id for both stored procedures. CREATE PROCEDURE MATHS.PITAGORAS (...)\nBEGIN\n  DECLARE LOGGER_ID SMALLINT;\n  CALL LOGGER.GET_LOGGER('maths', LOGGER_ID);\n  ...\nEND@\n\nCREATE PROCEDURE MATHS.FIBONACCI (...)\nBEGIN\n  DECLARE LOGGER_ID SMALLINT;\n  CALL LOGGER.GET_LOGGER('maths', LOGGER_ID);\n  ...\nEND@ As you can see, you can define the hierarchy as you want. LOG Procedure This is a stored procedure that invokes the utility to register an event (log), but it depends on the current configuration if the log is really stored or just by-passed. To call this stored procedure, you indicate the logger id (retrieved from GET_LOGGER ), the level id , and a message. Level id is a number between 0 and the number of levels defined in the LEVELS table. The default ones are: 0 - OFF 1 - FATAL 2 - ERROR 3 - WARN 4 - INFO 5 - DEBUG Note: The default level names are stored in lower case. The message contains what you will write into the log. When performing a concatenation, it is highly recommended to be sure that the strings being concatenated are not empty ( NULL ); if a NULL is passed, the result will be an empty string ( NULL ) and you will not be logging anything. The configuration will decide if the given message is actually written via the appender or not (just by-passed). For more information about how to configure log4db2 , please visit this section . A working logger. CALL LOGGER.LOG(LOGGER_ID, 4, 'A message logged in INFO level'); Depending on the configuration it will log (An active appender with INFO level active): XXXXX, 4, myRoutine, A message logged in INFO level A null string could be: SET value = NULL;\nCALL LOGGER.LOG(LOGGER_ID, 2, 'The value for this key is ' || value); This will write: XXXXX, 2, myRoutine, NULL Macros There are some macros for the default levels. They reduce the number of parameters to pass to the stored procedure by changing the name of this last. With the macros, you do not need to recall the ID number for each level. For example, if you want to write a log with Warn level, you could use: CALL LOGGER.WARN(LOGGER_ID, 'The application has started'); Instead of: CALL LOGGER.LOG(LOGGER_ID, 3, 'The application has started'); In a similar way for the other 5 levels ( OFF does not have macro because it never writes a log): CALL LOGGER.FATAL(LOGGER_ID, 'Dump stack trace');\nCALL LOGGER.ERROR(LOGGER_ID, 'File not found');\nCALL LOGGER.INFO(LOGGER_ID, 'Finishing process');\nCALL LOGGER.DEBUG(LOGGER_ID, 'The value ' || VALUE || ' is bigger that ' || MAX); For a complete example, please check the source code src/examples/sql-pl . The description of these examples is on the Examples page . Administration The usage of this utility implies: Consult the generated logs. Consult and modify the current configuration. The utility has a set of stored procedures for different tasks. Administration objects The following table shows the objects to be used to manage the utility. Routine name Type Description LOGGER.ACTIVATE_CACHE* Proc Activates the cache. LOGGER.DEACTIVATE_CACHE* Proc Cleans the cache and deactivates it. LOGGER.GET_DEFINED_PARENT_LOGGER Func For a given logger returns the closer ascendancy that has a defined logger level. LOGADMIN.LOGS Proc Shows the last 100 log messages truncated to 72 characters with the hour (not the whole timestamp). LOG_MESSAGES View Retrieves the log messages with the date, the logger level name, and the whole logger name. LOGGER.MODIFY_DESCENDANTS Proc Modify the logger level of a logger with all its descendants. LOGADMIN.NEXT_LOGS Proc Shows the log messages by pages, truncating the message to 72 characters with the hour (not the whole timestamp). REFRESH_CONF Proc Refreshes the cache configuration immediately. LOGADMIN.RESET_TABLES Proc Deletes all rows, and leaves the basis tables as they were after the installation. LOGADMIN.REGISTER_LOGGER_NAME Proc Register a logger and specify a level name. LOGADMIN. REGISTER_LOGGER Proc Register a logger and specify a level. LOGGER.SHOW_CACHE* Proc Shows the content of the logger cache if it is currently used. LOGGER.SHOW_CONF Proc Shows the current content of the configuration cache and information about its freshness. LOGADMIN.SHOW_LOGGERS Proc Returns a list of the loggers registered in the utility. (*) Cache operations will be removed. This will be the default option. Appenders This is the list of appenders. Appenders are the mechanisms to write or process the messages generated by the utility. They are never called directly from the user code, but instead, there are internally invoked by log4db2 . Routine name Name Internal Code Description LOG_CGTT CGTT 3 Writes the messages in a Created Global Temporary Table. LOG_DB2DIAG DB2DIAG 5 Sends the log message to the db2diag.log file*. LOG_DB2LOGGER DB2LOGGER 6 Sends the log message to the DB2LOGGER utility*. LOG_JAVA Java 7 Sends the log message to a Java Stored Procedure*. LOG_NULL Null 0 Drops the log message. LOG_STDOUT StdOut 4 Writes the message in the standard output of the current session. LOG_TABLES Tables 1 Writes the log message to a table (Same transaction). LOG_TABLES_AUTONOMOUS Tables 1 Writes the log message to a table with an autonomous procedure (Default one). LOG_UTL_FILE UTL_FILE 2 Writes the log message to an external file. (*) These appenders are not yet developed. Some appenders can have specific configuration. For example, the layout of a message is defined in CONF_APPENDERS . For more information about the possible values, please check the configuration section. Query the logs You can query the logs in different ways: Directly from the LOGDATA.LOGS . However, there are some hidden columns, and the logged level and logger are givens as IDs. Thus, you have to do the joins between tables. Using the view LOGGER_X.LOG_MESSAGES . This view executes the underlying query to join the tables, and you get information that can be easily read. X is the log4db2 version. With the LOGADMIN.LOGS procedure. It returns the 100 more recent rows of the table, with the messages truncated to 72 characters, and the hour (no date.) Here some examples: SELECT * FROM logs;\nSELECT * FROM logger_X.log_messages;\nCALL logadmin.logs() Modify the logger hierarchy General configuration First, to check the current configuration, you can use the SHOW_CONF stored procedure. CALL logger.show_conf(); To change the configuration, you just modify the configuration table UPDATE logger_X.configuration\n  SET value = Y\n  WHERE key = Z; Where X is the log4db2 version, Y the value to use, and Z the name of the configuration parameter. If you want to force the configuration reload, please execute: CALL logger.refresh_conf(); Loggers configuration First, to see the current configuration you can obtain a list of registered loggers by executing: CALL logger.show_loggers(); If you want to modify you one level, you issue the DML directly on the database UPDATE logger_X.conf_loggers\n  SET level_id = Y\n  WHERE logger_id = Z; Where X is the log4db2 version, Y is the level Id to insert, Z is the logger ID. For the logger_id , you can obtain it by: CALL logger.get_logger(W); Where W is the logger name. If you want to modify a given logger and all its descendants, then use the following stored procedure: CALL logger.modify_descendants(X, Y); Where X is the logger ID and Y is the level ID. Also, if you only one to modify a specific logger, you can do it by calling the following stored procedures, providing the name or the id of the level: CALL logadmin.registe_logger_name(X, LEVEL_NAME);\nCALL logadmin.registe_logger(X, LEVEL_ID); Remove without affecting existing routines Probably, you could need to remove log4db2 but you already have several routines that use it, and you do not want to modify them. Instead of uninstall it, you could use one of the examples, which is call a fake installation. In fact, this example creates the mail routines with an empty body, and nothing is impacted. Your routines will continue working and invoking the log4db2 functions and stored procedures, but they will do nothing and return the control to your routines. You can read more about it in the examples section .","filename":"Usage.md","format":"markdown","hl_body":"...  functions MODIFIES SQL DATA . The user used to execute your routines should be able to execute the log4db2 routines. <em>Usage</em> in the source code NOTE : Each time you call log4db2 make sure the message you are ...","hl_title":"<em>Usage</em>","id":"cc1ae92bd5bbb0dedaf7c59a13d806d7574b9419","path":"docs/Usage.md","public":true,"repo":{"repository":{"id":5734579,"name":"log4db2","owner_id":294317,"owner_login":"angoca","updated_at":"2022-06-10T02:41:51.013Z","has_issues":true}},"repo_id":5734579,"title":"Usage","updated_at":"2022-06-11T19:09:29.000-05:00"},{"body":"Usage and getting help ( Return to ToC ) get_iplayer itself can provide brief usage examples and descriptions of available options.  Because there are quite a few options, help listings are available at three levels of detail: get_iplayer --help\nget_iplayer --basic-help\nget_iplayer --long-help Linux/BSD/macOS users who installed a packaged version of get_iplayer may have access to a manual page: man get_iplayer The get_iplayer UNIX manual page listing all available options can be viewed here . A full list of all available options in both command line and options file formats can be viewed here . Web PVR Manager users should click the Help button at the top right of the user interface to go here . A list of frequently asked questions can be found here . Other resources: Tutorials","filename":"usage.md","format":"markdown","hl_body":"<em>Usage</em> and getting help ( Return to ToC ) get_iplayer itself can provide brief <em>usage</em> examples and descriptions of available options.  Because there are quite a few options, help listings are available ...","hl_title":"<em>usage</em>","id":"910ee1febce34787828a1339750fc1b40d1df66b","path":"usage.md","public":true,"repo":{"repository":{"id":1469734,"name":"get_iplayer","owner_id":9755374,"owner_login":"get-iplayer","updated_at":"2024-01-14T20:09:44.245Z","has_issues":true}},"repo_id":1469734,"title":"usage","updated_at":"2020-07-06T13:49:26.000+01:00"},{"body":"Usage To create a skeleton wombat project run the following command: $ wombat init In this skeleton project a sample wombat.yml file will be generated.  Please refer to the Configuration page for more information about this file. The googlecompute builder exists, but not all images will build nor is there deployment support for it at this time. Building images with Packer Once the project has been configured the wombat command can be used to build images using packer. $ wombat build [-o BUILDER] TEMPLATE [TEMPLATE2] Code Listing 1 : Build image from one or more templates $ wombat build [-o BUILDER] Code Listing 2 : Build all images sequentially $ wombat build [-o BUILDER] --parallel Code Listing 3 : Build all images in parallel The supported builders that can be specified in this command are: amazon-ebs azure-arm If no builder is given then amazon-ebs will be used. For Cloud specific instructions please refer to the following: AWS Azure","filename":"Usage.md","format":"markdown","hl_body":"<em>Usage</em> To create a skeleton wombat project run the following command: $ wombat init In this skeleton project a sample wombat.yml file will be generated.  Please refer to the Configuration page for ...","hl_title":"<em>Usage</em>","id":"d4cc77799ca55b37134279b7141a2031e263a9d8","path":"Usage.md","public":true,"repo":{"repository":{"id":59371937,"name":"wombat","owner_id":13543320,"owner_login":"chef-cft","updated_at":"2021-08-24T12:55:33.938Z","has_issues":true}},"repo_id":59371937,"title":"Usage","updated_at":"2017-02-15T16:00:52.000Z"},{"body":"The application presents three possible screens (activities) for interaction. Main Screen Selection Screen Recording Screen Summary Screen Main Screen / Selection Screen: the first screen shown after the app is open, there is a box list for the feature selection. Recording Screen: a little timer clock shows up indicating the recording started and its duration, the recording action can be paused/resumed pressing the same button that was used to start the action. Summary Screen: this activity is shown after the finish button is pressed in the recording screen, a chart is presented with the percentage of speaking time form each detected speaker.","filename":"Usage.md","format":"markdown","hl_body":"The application presents three possible screens (activities) for interaction. Main Screen Selection Screen Recording Screen Summary Screen Main Screen / Selection Screen: the first screen shown after the ...","hl_title":"<em>Usage</em>","id":"9423167c47cfd634887dfc720f0851eee13f9b6e","path":"Usage.md","public":true,"repo":{"repository":{"id":61066316,"name":"convMod","owner_id":929171,"owner_login":"marcossilva","updated_at":"2016-07-20T19:20:59.720Z","has_issues":true}},"repo_id":61066316,"title":"Usage","updated_at":"2016-07-21T13:34:23.000-05:00"},{"body":"So far, there are two ways of using Krextor: on the command line, either by using the provided ShellScript (recommended), or by manually running an XSLT processor from a Java program, either by using our JavaWrapper (recommended), or by manually by running the XSLT, e.g. via JAXP","filename":"Usage.md","format":"markdown","hl_body":"So far, there are two ways of using Krextor: on the command line, either by using the provided ShellScript (recommended), or by manually running an XSLT processor from a Java program, either by using our ...","hl_title":"<em>Usage</em>","id":"42f09c10013c52abf493329137aab20047d24782","path":"Usage.md","public":true,"repo":{"repository":{"id":60781270,"name":"krextor","owner_id":6399175,"owner_login":"EIS-Bonn","updated_at":"2016-10-05T14:44:12.817Z","has_issues":true}},"repo_id":60781270,"title":"Usage","updated_at":"2016-06-14T12:02:05.000+02:00"},{"body":"Usage Pssst... The first steps in order to use this software are installing all it's Dependencies and generating the References it will use when running. Once those previous steps are taken, you can start analyzing your samples. Take a look at the Directory Structure in order to understand how the analysis output is organized. All the directories of the analysis are created automatically except for ANALYSIS/00-reads, where you should place your raw fastq.gz files. Also all the directories below REFERENCES must be exactly as they appear on the Directory Structure , including the file names. In the References page you will find all the necessary steps to create the structure. All set? Great! So you have made sure you have everything you need to make this run. Let's run it!. The gist of the analysis is as follows: Quality control : trims your reads and makes them neat and beautiful for the next steps of the analysis. Host filtering : filters out all the reads of the host to make the rest of analysis cleaner. Mapping against reference : Maps your reads to the bacteria, virus, fungi or parasite (Invertebrate and Protozoa) reference and saves all those that match. Assembly : Tries to assemble the reads in each group (bacteria, virus, fungi and parasite) to make longer contigs. Blast : Runs blast of each of the contigs generated in the previous step against the corresponding database. Coverage : Calculates the coverage for each of the genomes in the reference and creates depth graphs.\nNote that the coverage can be calculated immediately after the third step ( Mapping ). Generating Results But I want to analyze several samples at once If you want to analyze several samples you must simply run the Sample Name list generator and then proceed as explained above, using the wrapper scripts explained in each section.","filename":"Usage.md","format":"markdown","hl_body":"<em>Usage</em> Pssst... The first steps in order to use this software are installing all it&#x27;s Dependencies and generating the References it will use when running. Once those previous steps are taken, you can","hl_title":"<em>Usage</em>","id":"184f10098e7b22340ac739aa12a60f5d1bc5a8ab","path":"Usage.md","public":true,"repo":{"repository":{"id":61368957,"name":"METAGENOMICS","owner_id":6838299,"owner_login":"AndreaRP","updated_at":"2017-02-28T11:05:21.995Z","has_issues":true}},"repo_id":61368957,"title":"Usage","updated_at":"2016-09-20T12:15:35.000+02:00"},{"body":"Broadcast Manager The broadcast manager is available as a service ekko.broadcast.manager . # your service.yml services : my.service : class : Namespace\\Of\\MyService arguments :\n      - \" @ekko.broadcast.manager \" // My service class namespace Namespace \\ Of \\ MyService ; use EdwinLuijten \\ Ekko \\ BroadcastManager ; class MyService { public function _construct ( BroadcastManager $ broadcastManager )\n    { $ this - > broadcasteManager = $ broadcastManager ;\n    } public function helloWorld ()\n    { // Set a default broadcaster $ this - > broadcastManager - > setDefaultBroadcaster ( new SomeBroadcaster ( new Client ())); // Add a broadcaster $ this - > broadcastManager - > add ( 'my-broadcaster' , new SomeBroadcaster ( new Client ())); // Calls broadcast on the default broadcaster $ this - > broadcastManager - > broadcast ([ 'my_channel' ], 'my_event' , [ 'message' = > 'hello-world' ]); // Calls broadcast on a specific broadcaster $ this - > broadcastManager - > connection ( 'my-broadcaster' )- > broadcast ([ 'my_channel' ], 'my_event' , [ 'message' = > 'hello-world' ]);\n    }\n} Configure a broadcaster","filename":"Usage.md","format":"markdown","hl_body":"Broadcast Manager The broadcast manager is available as a service ekko.broadcast.manager . # your service.yml services : my.service : class : Namespace\\Of\\MyService arguments :\n      - &quot; @ekko.broadcast.manager ...","hl_title":"<em>Usage</em>","id":"814ea1c1d1f9dfeb7eb26e708efcf247ded9f6a8","path":"Usage.md","public":true,"repo":{"repository":{"id":64819066,"name":"ekko-broadcast-bundle","owner_id":1339637,"owner_login":"Edwin-Luijten","updated_at":"2016-08-17T07:39:40.322Z","has_issues":true}},"repo_id":64819066,"title":"Usage","updated_at":"2016-08-08T14:28:49.000+02:00"}],"type":"wikis","page":1,"page_count":100,"elapsed_millis":368,"errors":[],"result_count":191730,"facets":[],"protected_org_logins":[],"topics":null,"query_id":"","logged_in":false,"sign_up_path":"/signup?source=code_search_results","sign_in_path":"/login?return_to=https%3A%2F%2Fgithub.com%2Fsearch%3Fq%3Dusage%2Bupdated%253A%253E2016-01-01%26type%3DWikis","metadata":null},"title":"Wiki search results"}