I have another question, so far I know that users ...
# kotlinx-rpc
d
I have another question, so far I know that users have 2-3 primary use cases for this library: 1) client to server communication a) the client is a browser b) the client is an android or iOS app 2) server to server communication Also from this chat I found that there are some known limitations of this lib: 1) the connection can get lost after a long inaction - can it happen for all listed above scenarios? 2) If I build a micro-services based design for my app on top of kRPC (server to server), what are other things I should be aware of?