• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

Search results

  1. F

    .Net Core OT Producer/Consumer model

    Asio from boost isn't a single loop, it starts a crazy amount of thread to manage the connections. Similar for the scheduler used in the game logic. It reminds me of some projects that I had to fix at work where people were going overboard in async coding where it wasn't needed. Tfs isn't as bad...
  2. F

    .Net Core OT Producer/Consumer model

    I am not using this implementation anymore, but I never had this issue over numerous tests when I did. Are you sure that your buffer is filled correctly everytime? 1580613724 On single core, everything will be happening in a single loop with priority based on timing. On multiple cores one...
  3. F

    .Net Core OT Producer/Consumer model

    Yeah, the RSA part was a pain to implement. There was a lot of testing to get it working. If you look at the SharpOT project on github you will see how it got implemented in this project, which works. It isn't the cleanest implementation, but starting with it you should be able to set up a...
  4. F

    .Net Core OT Producer/Consumer model

    This fibula project does look very clean, yes. It is not my type of coding though, so I won't join on the effort. It uses a lot of external ressources which creates a bunch of overhead in their network communication and such. They also use an approach that put enormous strain on the garbage...
  5. F

    .Net Core OT Producer/Consumer model

    I am developing my own engine in C# . My goal is to create an engine that work with Parallel tasks that all take care of a part of the system in a non blocking way, instead of a Scheduler to reduce the amount of context changes. I am designing it for my own project so the goal is not to create...
Back
Top Bottom