Author |
Message |
Topic: Ideas for API improvement |
Dal
Replies: 6
Views: 9680
|
Forum: General Discussion Posted: Wed Mar 30, 2005 16:34 Subject: Ideas for API improvement |
Ok, seems I misunderstood a few things too. The NWN and NWNX client processes aren't related at all, so function pointers are out. At the moment I'd have to use named pipes or something similar to pas ... |
Topic: Multithreading database access? |
Dal
Replies: 11
Views: 15591
|
Forum: Database related Posted: Wed Mar 30, 2005 16:21 Subject: Multithreading database access? |
That's a nice, clean solution, NoMercy.. assuming the first While is really supposed to be an If and it's called as a feature of a plugin and not a standard requirement to treat all queries that way. ... |
Topic: Multithreading database access? |
Dal
Replies: 11
Views: 15591
|
Forum: Database related Posted: Wed Mar 30, 2005 15:19 Subject: Multithreading database access? |
That query string is a monster, maybe turning it into a stored procedure might speed things up slightly. |
Topic: Ideas for API improvement |
Dal
Replies: 6
Views: 9680
|
Forum: General Discussion Posted: Wed Mar 30, 2005 14:25 Subject: Ideas for API improvement |
Right, I'll explain myself a bit better:
Dot NET apps are compiled into something called the Common Language Runtime (CLR), this is interpretted when the app runs but turned into native code (ie. a ... |
Topic: Ideas for API improvement |
Dal
Replies: 6
Views: 9680
|
Forum: General Discussion Posted: Tue Mar 29, 2005 17:39 Subject: Ideas for API improvement |
1) In 10 minutes I'v just moved the process-handling global functions from the NWNX exe project into the NWNX-module DLL, added a .def file exposing them and now the server process starts fine.
I a ... |
Topic: Ideas for API improvement |
Dal
Replies: 6
Views: 9680
|
Forum: General Discussion Posted: Mon Mar 28, 2005 18:12 Subject: Ideas for API improvement |
NWNX is great, but I'd like to discuss a few refactoring ideas for the NWNX API..
1) Making the NWN process DLL injection and hooking a responsibility of the DLL itself - where it rightly belongs, ... |
|