cdparra / globalengage Goto Github PK

Right now, the demo supports only one global event at at time. To enable multiple events, the community front should

• Send the "eventKey" to the hangout app when this is started
• Store the "eventKey" attached to its information in the webdis server

To support multiple events, the different front-ends should use the same data model to store, retrieve and delete:

• Events List (by range)
• Events Keys
• Events Hangouts

We need to create a common webdis client shared between front-ends

Right now, the demo supports only one global event at at time. To enable multiple events in the connect front-end, this should:

• Retrieve the "eventList" from the webdis server.
• Attach each event box to the correct "eventKey"
• When querying for the eventKey does not returns a valid Hangout url, show that the event is not available

Right now, the demo supports only one global event at a time. To enable multiple events, the hangout app should:

• Retrieve the "eventKey" from the community front-end
• Store the "hangoutUrl" as a value for the "eventKey" on the server

To make the prototype useful for anyone that downloads the source code, we need to add an easy way to configure all the parameters for web app to function:

• Where is the webdis server running?
• Where is the hangout app running?
  etc..