Clients receive their own events #6

Closed
opened 2017-03-03 02:36:48 +00:00 by jamie · 2 comments
jamie commented 2017-03-03 02:36:48 +00:00 (Migrated from git.hazaar.io)

This probably should not happen unless requested. There really is no need for a client to receive their own event as correctly written code should take the data being sent in the trigger and use it locally for better efficiency.

However, I think a new flag on the trigger function could be used to request that the data is echo'd. The server can then echo the event back to the triggering client.

This probably should not happen unless requested. There really is no need for a client to receive their own event as correctly written code should take the data being sent in the trigger and use it locally for better efficiency. However, I think a new flag on the trigger function could be used to request that the data is echo'd. The server can then echo the event back to the triggering client.
jamie commented 2017-03-03 02:49:39 +00:00 (Migrated from git.hazaar.io)

Completed in 3ad95dcbd7

Completed in 3ad95dcbd7cd719d3a57d658c8940fb1614c8ddd
jamie commented 2017-03-03 02:49:42 +00:00 (Migrated from git.hazaar.io)

closed

closed
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: hazaar/hazaar-warlock#6
No description provided.