C Server Daemon Developpment

I look forward to discuss further about the project details and deliver the same to your needs .

I am very proficient in c, c++. I have 15 years c++ developing experience now, and I have worked for 5 years. My work is online game developing, and mainly focus on server side, the language is c++ under linux. I used c++ to make many great projects, for example, I made the tools which can convert java files to c++ scripts which has the same effect, of course garbage collection included. I also made our own mobile game using c++, I even can show you the demo of client. Trust me, please let expert help you.

I have some experience of maintaining C++ daemons and Ada server. Preferably I would implement your project in Ada, this will be less error-prone as my experience shows, but I can also use pthreads and C if required. There are different designs of such servers. It can be implemented as single-thread async server (libev, libevent, libuv), but many libraries (e. g. mysql connector) are still implemented in sync mode, so multi-threaded design is less risky in general.

Bonjour :-). I have implemented functionality like the one you need, only in a slightly different manner; it's commercially-used, as part of a networking appliance currently sold by a well-known security company (I have a confidentiality agreement with them, so I cannot offer too many details, but if you have a look at my CV, you can figure out what device and what company I'm talking about; it sort of starts with B and ends with itdefender...). I have a few suggestions/questions: 1. What amount of traffic are we talking about here? 2. Do you need any kind of pre-query authentication (i.e. have users send subscription data first, so that you don't serve to users who aren't yours)? 3. Are you sure the method you want to use is the one you are looking after? It *does not* handle client-side DNS caching correctly! I chose a different (if more complicated) solution the last time I did this, through a transparent web proxy. Of course, we also needed other features (such as *specific* content blocking), but DNS caching on the client side was one reason why we didn't follow this route. 4. What you describe in the document is essentially a DNS proxy; are you convinced you don't need that kind of functionality added into BIND? BIND is open source; its source code is pretty messy so it may take a little longer, but it is possible to add a pre-caching layer to it. Is it a route you explored? Best regards, Alexandru