Page Comparison

...

• complete the Pico Engine Quickstart
• have the hello_world ruleset from the Quickstart registered in the pico - engine, and installed in a pico
• have installed the event console in Google Chrome

...

• "http://" identifies HTTP as the protocol
• "localhost:8080" is the domain name and port of the pico - engine which hosts the pico
• "sky/event" identifies this as an event for the pico
• "citdel5gz00012aaoo5ucc613" is one of the pico's event channel identifiers (ECI) (yours will be different)
• "1556" is an arbitrary string which serves as an event identifier (EID) and correlation ID. (useful when looking at logs)
• "echo" identifies the domain of the event
• "hello" identifies the type of the event
  

...

As you can see in the URL for events and queries, channels are the way in which a pico can be identified by the pico - engine.

A pico can have multiple channels. Best practice is to create a channel for each purpose or correspondent. There are several reasons for this:

...

...

The Kynetx event console is a Google Chrome application that you can add to your browser to make it easy to send events. You can find it on githubGitHub and install it into your browser following the instructions. You can then launch it and enter in the host:port of your pico engine, the channel identifier and the event domain and type. You will need to un-check the box beside "Use HTTPS".

...

Be sure to validate your source code, using one of the techniques in Developer Tips for Pico Engine to ensure that you have introduced no syntax errors into your ruleset. Once you get the "ok", go ahead and push your changes into Github GitHub and re-install the ruleset into your pico. (Review the Pico Engine Quickstart page if necessary)

...

Look at the console from which you started your pico - engine.

You should see entries like this one:

...

After making these changes to your ruleset, be sure to validate it, then push your change to GithubGitHub, and re-install into your pico.

...