<commit_before>sp_pair(7)
==========

NAME
----
sp_pair - one-to-one messaging pattern


SYNOPSIS
--------
*#include <sp/sp.h>*

*#include <sp/pair.h>*


DESCRIPTION
-----------
PAIR pattern.


SEE ALSO
--------
linknanomsg:sp_socket[3]
linknanomsg:sp_getsockopt[3]
linknanomsg:sp_setsockopt[3]
linknanomsg:nanomsg[7]


AUTHORS
-------
<NAME> <<EMAIL>>
<commit_msg>sp_pair(7) man page filled in<commit_after>sp_pair(7)
==========

NAME
----
sp_pair - one-to-one messaging pattern


SYNOPSIS
--------
*#include <sp/sp.h>*

*#include <sp/pair.h>*


DESCRIPTION
-----------
Pair pattern is the simplest and least scalable messaging pattern. It allows
scaling by breaking the application in exactly two pieces. For example,
if a monolithic application handles both accounting and agenda of HR department,
it can be split into two applications (accounting vs. HR) that are run on two
separate servers. These applications can then communicate via PAIR sockets.

The downside of this pattern is that its scaling properties are very limited.
Splitting the application into two pieces allows to scale to two servers.
To add the third server to the cluster, application has to be split once more,
say be separating HR functionality into hiring module and salary computation
module. Whenever possible, try to use one of the more scalable patterns instead.

Socket Types
~~~~~~~~~~~~

SP_PAIR::
    Socket for communication with exactly one peer.

Socket Options
~~~~~~~~~~~~~~

No protocol-specific socket options are degined at the moment.

SEE ALSO
--------
linknanomsg:sp_pubsub[7]
linknanomsg:sp_reqrep[7]
linknanomsg:sp_fanin[7]
linknanomsg:sp_fanout[7]
linknanomsg:sp_survey[7]
linknanomsg:nanomsg[7]


AUTHORS
-------
<NAME> <<EMAIL>>

{'fraction_non_alphanumeric': 0.1340265742345465, 'fraction_numerical': 0.007510109763142692, 'mean_word_length': 4.049562682215743, 'pattern_counts': {'":': 0, '<': 13, '<?xml version=': 0, '>': 13, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4499937', 'n_tokens_mistral': 558, 'n_tokens_neox': 534, 'n_words': 195}