Keystroke Observers - Revision history

Jwgranville: Disambiguated terms in explanation

2025-06-26T22:15:24Z

Disambiguated terms in explanation

← Older revision		Revision as of 22:15, 26 June 2025
Line 16:		Line 16:
	LineByLineTotalizer buffers incoming data until a newline character is observed, similar to analyze.py used in previous versions. There has previously been interest in the timing not just between newlines, but all keystrokes. But analyze.py does not record this.		LineByLineTotalizer buffers incoming data until a newline character is observed, similar to analyze.py used in previous versions. There has previously been interest in the timing not just between newlines, but all keystrokes. But analyze.py does not record this.

	ImmediateTotalizer, FixedIntervalTotalizer and DynamicIntervalTotalizer demonstrate alternative policies for how often to count and potentially timestamp the contents of the input buffer. These classes implement the [[wikipedia:Observer_pattern\|Observer]] [https://typing.python.org/en/latest/spec/protocol.html protocol] (update()), allowing them to respond to messages broadcast from Subject instances. See observerdemo_0_1_1.py.		ImmediateTotalizer, FixedIntervalTotalizer and DynamicIntervalTotalizer demonstrate alternative policies for how often to count and potentially timestamp the contents of the input buffer. These classes implement the [[wikipedia:Observer_pattern\|Observer]] pattern as a Python [https://typing.python.org/en/latest/spec/protocol.html protocol] (update()), allowing them to respond to messages broadcast from Subject instances. See observerdemo_0_1_1.py.

	By broadcasting log events to all Observer instances, every log processor can have equal access to the original log data without resource conflicts or individual synchronization. See toy_logger_tcp_0_1_3.py.		By broadcasting log events to all Observer instances, every log processor can have equal access to the original log data without resource conflicts or individual synchronization. See toy_logger_tcp_0_1_3.py.

	Rather than continue to modify and grow the features/responsibilities of analyze.py, I propose this method of creating a data pipeline that obeys the [[wikipedia:Open–closed_principle\|Open-Closed Principle]], meaning that it is closed to code changes, but open to behavior extension by means of a pluggable interface; in this example, Subject.attach(). See observerdemo_0_1_1.py.		Rather than continue to modify and grow the features/responsibilities of analyze.py, I propose this method of creating a data pipeline that obeys the [[wikipedia:Open–closed_principle\|Open-Closed Principle]], meaning that it is closed to code changes, but open to behavior extension by means of a pluggable interface; in this example, Subject.attach(). See observerdemo_0_1_1.py.

Jwgranville: Touch up style

2025-06-20T18:53:47Z

Touch up style

← Older revision		Revision as of 18:53, 20 June 2025
Line 5:		Line 5:

	== Instructions ==		== Instructions ==
	To run it one can start `./[https://github.com/edurange/demo-keystroke-observers/blob/main/toy_logger_tcp_0_1_3.py toy_logger_tcp_0_1_3.py]`. Then, connect to local port 5554 and 5555 with a TTY utility such as [https://netcat.sourceforge.net netcat]: `nc 127.0.0.1 5554`. 5554 mocks the behavior of ttylog and analyzes the input received. 5555 demonstrates that another interface, such as the guide or web GUI, could be simultaneously monitored and handled by different behavior.		To run it one can start:
			./[https://github.com/edurange/demo-keystroke-observers/blob/main/toy_logger_tcp_0_1_3.py toy_logger_tcp_0_1_3.py]
			Then, connect to local port 5554 and 5555 with a TTY utility such as [https://netcat.sourceforge.net netcat]:
			nc 127.0.0.1 5554
			5554 mocks the behavior of ttylog and analyzes the input received. 5555 demonstrates that another interface, such as the guide or web GUI, could be simultaneously monitored and handled by different behavior.

	== Explanation ==		== Explanation ==

Jwgranville at 20:41, 30 May 2025

2025-05-30T20:41:34Z

← Older revision		Revision as of 20:41, 30 May 2025
Line 1:		Line 1:
	[[Category:Demonstrations]]		[[Category:Demonstrations]]
	~~dSee~~ https://github.com/edurange/demo-keystroke-observers.		See https://github.com/edurange/demo-keystroke-observers.

	Demonstrates a one-writer-multiple-reader message topology for log processing.		Demonstrates a one-writer-multiple-reader message topology for log processing.

Jwgranville at 20:39, 30 May 2025

2025-05-30T20:39:10Z

← Older revision		Revision as of 20:39, 30 May 2025
Line 16:		Line 16:
	By broadcasting log events to all Observer instances, every log processor can have equal access to the original log data without resource conflicts or individual synchronization. See toy_logger_tcp_0_1_3.py.		By broadcasting log events to all Observer instances, every log processor can have equal access to the original log data without resource conflicts or individual synchronization. See toy_logger_tcp_0_1_3.py.

	Rather than continue to modify and grow the features/responsibilities of analyze.py, I propose this method of creating a data pipeline that obeys the [[wikipedia:Open–closed_principle\|Open-Closed Principle]], meaning that it is closed to code changes, but open to behavior extension by means of a pluggable interface; in this example, ~~Observer~~.attach(). See observerdemo_0_1_1.py.		Rather than continue to modify and grow the features/responsibilities of analyze.py, I propose this method of creating a data pipeline that obeys the [[wikipedia:Open–closed_principle\|Open-Closed Principle]], meaning that it is closed to code changes, but open to behavior extension by means of a pluggable interface; in this example, Subject.attach(). See observerdemo_0_1_1.py.

Jwgranville: Add references

2025-05-30T20:37:58Z

Add references

← Older revision		Revision as of 20:37, 30 May 2025
Line 1:		Line 1:
	[[Category:Demonstrations]]		[[Category:Demonstrations]]
	~~See~~ https://github.com/edurange/demo-keystroke-observers.		dSee https://github.com/edurange/demo-keystroke-observers.

	Demonstrates a one-writer-multiple-reader message topology for log processing.		Demonstrates a one-writer-multiple-reader message topology for log processing.
Line 12:		Line 12:
	LineByLineTotalizer buffers incoming data until a newline character is observed, similar to analyze.py used in previous versions. There has previously been interest in the timing not just between newlines, but all keystrokes. But analyze.py does not record this.		LineByLineTotalizer buffers incoming data until a newline character is observed, similar to analyze.py used in previous versions. There has previously been interest in the timing not just between newlines, but all keystrokes. But analyze.py does not record this.

	ImmediateTotalizer, FixedIntervalTotalizer and DynamicIntervalTotalizer demonstrate alternative policies for how often to count and potentially timestamp the contents of the input buffer. These classes implement the Observer protocol (update()), allowing them to respond to messages broadcast from Subject instances. See observerdemo_0_1_1.py.		ImmediateTotalizer, FixedIntervalTotalizer and DynamicIntervalTotalizer demonstrate alternative policies for how often to count and potentially timestamp the contents of the input buffer. These classes implement the [[wikipedia:Observer_pattern\|Observer]] [https://typing.python.org/en/latest/spec/protocol.html protocol] (update()), allowing them to respond to messages broadcast from Subject instances. See observerdemo_0_1_1.py.

	By broadcasting log events to all Observer instances, every log processor can have equal access to the original log data without resource conflicts or individual synchronization. See toy_logger_tcp_0_1_3.py.		By broadcasting log events to all Observer instances, every log processor can have equal access to the original log data without resource conflicts or individual synchronization. See toy_logger_tcp_0_1_3.py.

	Rather than continue to modify and grow the features/responsibilities of analyze.py, I propose this method of creating a data pipeline that obeys the Open-Closed Principle, meaning that it is closed to code changes, but open to behavior extension by means of a pluggable interface; in this example, Observer.attach(). See observerdemo_0_1_1.py.		Rather than continue to modify and grow the features/responsibilities of analyze.py, I propose this method of creating a data pipeline that obeys the [[wikipedia:Open–closed_principle\|Open-Closed Principle]], meaning that it is closed to code changes, but open to behavior extension by means of a pluggable interface; in this example, Observer.attach(). See observerdemo_0_1_1.py.

Jwgranville: Add comments from code files

2025-05-30T20:22:51Z

Add comments from code files

← Older revision		Revision as of 20:22, 30 May 2025
Line 1:		Line 1:
	[[Category:Demonstrations]]		[[Category:Demonstrations]]
	https://github.com/edurange/demo-keystroke-observers		See https://github.com/edurange/demo-keystroke-observers.

			Demonstrates a one-writer-multiple-reader message topology for log processing.

			== Instructions ==
			To run it one can start `./[https://github.com/edurange/demo-keystroke-observers/blob/main/toy_logger_tcp_0_1_3.py toy_logger_tcp_0_1_3.py]`. Then, connect to local port 5554 and 5555 with a TTY utility such as [https://netcat.sourceforge.net netcat]: `nc 127.0.0.1 5554`. 5554 mocks the behavior of ttylog and analyzes the input received. 5555 demonstrates that another interface, such as the guide or web GUI, could be simultaneously monitored and handled by different behavior.

			== Explanation ==
			This is a proposal for a new communication strategy in the log pipeline. This would exist in a place analogous to the space between [https://github.com/edurange/edurange3/blob/main/scenarios/global_scripts/ttylog ttylog], [https://github.com/edurange/edurange3/blob/main/scenarios/global_scripts/analyze.py analyze.py] and [https://github.com/edurange/edurange3/blob/main/scenarios/global_scripts/milestone-lbl.pl milestone-lbl.pl] in the current implementation; see also https://github.com/edurange/edurange3/tree/main/scenarios/global_scripts.

			LineByLineTotalizer buffers incoming data until a newline character is observed, similar to analyze.py used in previous versions. There has previously been interest in the timing not just between newlines, but all keystrokes. But analyze.py does not record this.

			ImmediateTotalizer, FixedIntervalTotalizer and DynamicIntervalTotalizer demonstrate alternative policies for how often to count and potentially timestamp the contents of the input buffer. These classes implement the Observer protocol (update()), allowing them to respond to messages broadcast from Subject instances. See observerdemo_0_1_1.py.

			By broadcasting log events to all Observer instances, every log processor can have equal access to the original log data without resource conflicts or individual synchronization. See toy_logger_tcp_0_1_3.py.

			Rather than continue to modify and grow the features/responsibilities of analyze.py, I propose this method of creating a data pipeline that obeys the Open-Closed Principle, meaning that it is closed to code changes, but open to behavior extension by means of a pluggable interface; in this example, Observer.attach(). See observerdemo_0_1_1.py.

Jwgranville at 19:29, 30 May 2025

2025-05-30T19:29:33Z

← Older revision		Revision as of 19:29, 30 May 2025
Line 1:		Line 1:
	[[Category:Demonstrations]]		[[Category:Demonstrations]]
			https://github.com/edurange/demo-keystroke-observers

Jwgranville: Created page with "Category:Demonstrations"

2025-05-30T19:29:21Z

Created page with "Category:Demonstrations"

New page

[[Category:Demonstrations]]