Dr. Net! - Eugen Rieck wrote:
Maybe my old abandoned Pascal project is still of use for the structure:
I implemented only stubs, these just serialized the request and sent
it to a socket. On the other end there was a worker daemon
unserializing the call, doing the work, serializing the reply and
sending it back.
The idea behind that (and this part worked OK) was, that the worker
daemon could run on the same machine (use either socket to localhost
or named pipe) or on the server (use real network socket). The worker
daemon itself can do different things: Go to the Database directly
(e.g. Zarafa server or just a DB instance - MSSQL or MySQL or
whatever) or proxy to something else (Zarafa via API, Scalix, CalDAV,
etc.)
Yes IMHO this is absolutely the right way to do things.
My (finally unsolvable) problem was, that there was no good way for
memory management - using the functions from the MAPI helper object
was not really working from Free Pascal 1.x, all workarounds and hacks
ended in either extreme memory leaks (Read: Never free any memory) or
weird segfaults.
Microsoft C++ is your friend here :) But there is no reason why the code
should not be as portable as possible. Is there MinGW MAPI support?
Jerry.
------------------------------------------------------------------------------
_______________________________________________
otlkcon-devel mailing list
otlkcon-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/otlkcon-devel
