From e7087bcbc1e7c38f81f482a7ae1761d9e9db6232 Mon Sep 17 00:00:00 2001
From: Jocelyn Fiat <git@djoce.net>
Date: Mon, 29 Oct 2018 12:19:36 +0100
Subject: [PATCH] Added missing WSF_TIMEOUT_UTILITIES file.

---
 .../wsf/src/support/wsf_timeout_utilities.e   | 93 +++++++++++++++++++
 1 file changed, 93 insertions(+)
 create mode 100644 library/server/wsf/src/support/wsf_timeout_utilities.e

diff --git a/library/server/wsf/src/support/wsf_timeout_utilities.e b/library/server/wsf/src/support/wsf_timeout_utilities.e
new file mode 100644
index 00000000..051454d7
--- /dev/null
+++ b/library/server/wsf/src/support/wsf_timeout_utilities.e
@@ -0,0 +1,93 @@
+note
+	description: "Utility for timeout conversion."
+	author: "$Author$"
+	date: "$Date$"
+	revision: "$Revision$"
+	seealso: "See also {SOCKET_TIMEOUT_UTILITIES} from EiffelNet library."
+
+class
+	WSF_TIMEOUT_UTILITIES
+
+feature -- Time helpers
+
+	one_second_in_nanoseconds: NATURAL_64 = 1_000_000_000
+			-- Number of nanoseconds in one second.
+
+	one_millisecond_in_nanoseconds: NATURAL_64 = 1_000_000
+			-- Number of nanoseconds in one millisecond.
+
+	one_microsecond_in_nanoseconds: NATURAL_64 = 1_000
+			-- Number of nanoseconds in one microsecond.
+
+	max_timeout_ns_value: NATURAL_64 = 2_147_483_647_999_999_999
+			-- Maximum value for a timeout in nanoseconds.
+			-- See `is_valid_timeout_ns` for explanation.
+
+	nanoseconds_to_seconds (ns: NATURAL_64): INTEGER
+			-- Number of seconds in `ns` nanoseconds (that fits in INTEGER_32 value).
+			-- Warning: Result can not be more than {INTEGER}.max_value.
+		local
+			n64: NATURAL_64
+		do
+			n64 := ns // one_second_in_nanoseconds
+			if n64 > {INTEGER}.max_value.to_natural_64 then
+				Result := {INTEGER}.max_value
+			else
+				Result := n64.to_integer_32
+			end
+		ensure
+			non_negative: Result >= 0
+			coherent: Result.to_natural_64 * one_second_in_nanoseconds <= ns
+			is_class: class
+		end
+
+	seconds_to_nanoseconds (s: INTEGER): NATURAL_64
+			-- Number of nanoseconds in `s` seconds (that fits in NATURAL_64 value).
+		do
+			Result := one_second_in_nanoseconds * s.to_natural_64
+		ensure
+			is_class: class
+		end
+
+	milliseconds_to_nanoseconds (ms: INTEGER): NATURAL_64
+			-- Number of nanoseconds in `ms` milliseconds (that fits in NATURAL_64 value).
+		do
+			Result := one_millisecond_in_nanoseconds * ms.to_natural_64
+		ensure
+			is_class: class
+		end
+
+	microseconds_to_nanoseconds (us: INTEGER): NATURAL_64
+			-- Number of nanoseconds in `us` microseconds (that fits in NATURAL_64 value).
+		do
+			Result := one_microsecond_in_nanoseconds * us.to_natural_64
+		ensure
+			is_class: class
+		end
+
+feature -- Validation			
+
+	is_valid_timeout_ns (ns: NATURAL_64): BOOLEAN
+			--| Note: internally (C API), the ns timeout is splitted into:
+			--|  - a long value `tv_sec` : number of seconds
+			--|  - a long value `tv_usec`: number of microseconds (with struct timeval)
+			--| or in the future
+			--|  - a long value `tv_nsec`: number of nanoseconds  (with struct timespec)
+			--| tv_usec or tv_nsec should be >= 0 and < equivalent of 1 second.
+			--| tv_usec < 1_000_000
+			--| tv_nsec < 1_000_000_000
+			--| so there is no issue with NATURAL_64 for usec or nsec
+			--| but, then, there is restriction for the seconds value which is coded as long int
+			--|  and long values (32 bits) are between -2_147_483_647 and +2_147_483_647 (i.e 2e31 - 1 = {INTEGER_32}.max_value).
+			--|  then, the `seconds` part of the timeout <= +2_147_483_647, and then expressed in nanoseconds, and taking into account
+			--|  the usec or nsec part, the timeout should not be greater than:
+			--|     +2_147_483_647 * 1_000_000_000 + 999_999_999 =  2_147_483_647_999_999_999
+			--|      and as NATURAL_64's max value is bigger     = 18_446_744_073_709_551_615
+			--|      features dealing with timeout in nanoseconds have related preconditions.
+		do
+			Result := 0 <= ns and then ns <= max_timeout_ns_value
+		ensure
+			is_class: class
+		end
+
+end