Hoogle Search
Within LTS Haskell 24.52 (ghc-9.10.3)
Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.
DBusServerFlagsAuthenticationRequireSameUser :: DBusServerFlagsgi-gio GI.Gio.Flags Require the UID of the peer to be the same as the UID of the server when authenticating. (Since: 2.68)
-
gi-gio GI.Gio.Flags Flags used when querying a FileInfo.
FileQueryInfoFlagsNofollowSymlinks :: FileQueryInfoFlagsgi-gio GI.Gio.Flags Don't follow symlinks.
FileQueryInfoFlagsNone :: FileQueryInfoFlagsgi-gio GI.Gio.Flags No flags set.
contentTypeEquals :: (HasCallStack, MonadIO m) => Text -> Text -> m Boolgi-gio GI.Gio.Functions Compares two content types for equality.
appInfoEqual :: (HasCallStack, MonadIO m, IsAppInfo a, IsAppInfo b) => a -> b -> m Boolgi-gio GI.Gio.Interfaces.AppInfo Checks if two GAppInfos are equal. Note that the check *may not* compare each individual field, and only does an identity check. In case detecting changes in the contents is needed, program code must additionally compare relevant fields.
-
gi-gio GI.Gio.Interfaces.DtlsConnection Construct a GValueConstruct with valid value for the “require-close-notify” property. This is rarely needed directly, but it is used by new.
dtlsConnectionGetRequireCloseNotify :: (HasCallStack, MonadIO m, IsDtlsConnection a) => a -> m Boolgi-gio GI.Gio.Interfaces.DtlsConnection Tests whether or not conn expects a proper TLS close notification when the connection is closed. See dtlsConnectionSetRequireCloseNotify for details. Since: 2.48
-
gi-gio GI.Gio.Interfaces.DtlsConnection Sets whether or not conn expects a proper TLS close notification before the connection is closed. If this is True (the default), then conn will expect to receive a TLS close notification from its peer before the connection is closed, and will return a TlsErrorEof error if the connection is closed without proper notification (since this may indicate a network error, or man-in-the-middle attack). In some protocols, the application will know whether or not the connection was closed cleanly based on application-level data (because the application-level data includes a length field, or is somehow self-delimiting); in this case, the close notify is redundant and may be omitted. You can use dtlsConnectionSetRequireCloseNotify to tell conn to allow an "unannounced" connection close, in which case the close will show up as a 0-length read, as in a non-TLS DatagramBased, and it is up to the application to check that the data has been fully received. Note that this only affects the behavior when the peer closes the connection; when the application calls dtlsConnectionCloseAsync on conn itself, this will send a close notification regardless of the setting of this property. If you explicitly want to do an unclean close, you can close conn's DtlsConnection:baseSocket rather than closing conn itself. Since: 2.48
getDtlsConnectionRequireCloseNotify :: (MonadIO m, IsDtlsConnection o) => o -> m Boolgi-gio GI.Gio.Interfaces.DtlsConnection Get the value of the “require-close-notify” property. When overloading is enabled, this is equivalent to
get dtlsConnection #requireCloseNotify