Hi everyone, I hope you're doing great! As you may already know, I'm doing a small chat system to familiarize myself with Capnp before I do more ambitious things. I would like to have some sort of way to implement a banlist on the chat server. I do realize the whole point of capabilities is to have the same behavior no matter where the capability is called from. However, I feel like users (administrators) of server software are used to filter users by IP (when it comes to that). Alternatively, I'd like to find something unique (but persistent for a given computer - OS install? hardware? not sure) I could send during the handshake, to filter undesired users. Basically, I feel like I need some sort of persistent authentication system that's relatively hard to refresh, if I can't get access to the IP:port of the user even in the bootstrap object. I currently managed to hack pycapnp to get a method called on the bootstrap object when a client connects with IP and port as arguments, but even if I store them I have no way of knowing which client calls a given callback (which is a design choice I imagine).
I'd like to know your thoughts on the subject :-) thanks a lot in advance! -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to capnproto+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/capnproto.
