úÎ.)     None+BMNATS communication error#How often should we ping the server'Timeout interval for connect operationsHServer information sent usually upon opening a connection to NATS server&Message sent from the client to server.Message received by the client from the server/Advanced settings for connecting to NATS serverŒCalled when a client has successfully connected. This callback is called synchronously before the processing of incoming messages begins.%Called when a client is disconnected.AHost settings; may have different username/password for each host Username for authentication Password for authentication :Control structure representing a connection to NATS server Encode NATS client message!DDecode NATS server message; result is message + payload (payload is " in NatsSvrMsg)#!Returns next sid and updates MVar$=Generates a new INBOX name for request/response communication%%Create a TCP connection to the server&0Send a message and register callback if possible',Do the authentication handshake if necessary("Open and authenticate a connection)JMain thread that reads events from NATS server and reconnects if necessary*3Forever read input from a connection and process itConnect to a NATS server ,Connect to NATS server using custom settings:Subscribe to a channel, optionally specifying queue group Unsubscribe from a channel@Synchronous request/response communication to obtain one messageLSynchronous request/response for obtaining many messages in certain timespanPublish a messageDisconnect from a NATS server_+,-./0123456789:;<=>?@ABCDEFGHI JKLMNOPQRSTUV SID of subscriptionSubjectMessage Reply subjectWXY !#$%Z4If true, wait for the connection to become available-Action to do when the connection is available&[\'()$inifinite list of connections to try]*^4URI with format: nats://user:password@localhost:4222SubjectQueueCallbackSID of subscriptionSubjectRequestResponseSubjectBodyTimeout in microsecondsSubjectData_SubjectData`ab    0+,-./01234567=<;:98>? EDCBA@FGHI JKLMNOPQRSTUV WXY !#$%Z&[\'()]*^_`abNoneHMPublish a messageySubscribe to a channel, optionally specifying queue group If the JSON cannot be properly parsed, the message is ignoredSubjectDataSubjectQueueCallbackSID of subscriptionSubjectBodyTimeout in microsecondsc      !"#$%&'()*++,-./0123456789:;;<=>?@ABCDE FGHIJKLLMNOPQRSTUVWXYZ[\nats-queue-0.1.2.0 Network.NatsNetwork.Nats.Json NatsException NatsSettings natsHosts natsOnConnectnatsOnDisconnectNatsHost natsHHost natsHPort natsHUser natsHPassNats MsgCallbackNatsSIDdefaultSettingsconnectconnectSettings subscribe unsubscriberequest requestManypublish disconnect pingIntervaltimeoutIntervalNatsServerInfoNatsClntMessageNatsSvrMessage makeClntMsg decodeMessagebaseGHC.Err undefined newNatsSidnewInboxconnectToServer sendMessage authenticateprepareConnectionconnectionThreadconnectionHandlerNatsConnectionOptions natsConnUser natsConnPassnatsConnVerbosenatsConnPedanticnatsConnSslRequireddefaultConnectionOptions$fExceptionNatsExceptionnatsSvrAuthRequired$fToJSONNatsConnectionOptionsNatsClntConnectNatsClntPublishNatsClntUnsubscribeNatsClntSubscribe NatsClntPong NatsClntPingSubject NatsSvrInfo NatsSvrPong NatsSvrPing NatsSvrError NatsSvrOK NatsSvrMsg msgSubjectmsgSidmsgTextmsgReply natsSettings natsRuntime natsThreadId natsNextSid natsSubMap FifoQueueNatsSubscription subSubjectsubQueue subCallbacksubSid subjectToStr makeSubjectensureConnection timeoutThrow _sendMessage pingerThreadconnectionHandler'publish' $fReadNatsSID $fShowNatsSID$fToJSONNatsServerInfo