Re: [harbour-users] Abridged summary of harbour-users@googlegroups.com - 1 update in 1 topic
36 views
Skip to first unread message
Antonio Linares
May 9, 2026, 10:10:53 AM (22 hours ago) May 9
to harbou...@googlegroups.com
Dear Pritpal,
Yes, OpenADS implements both client and server.
Server: openads_serverd (Windows/Linux/macOS binaries in every release). Speaks an OpenADS-native TCP wire
protocol; clients connect via:
AdsConnect60("tcp://host:port/data_dir", ...)
The same ace64.dll / ace32.dll / libace64.so / libace64.dylib also runs as LocalServer (in-process
DLL, no daemon needed) selected via:
AdsConnect60(path, ADS_LOCAL_SERVER, ...)
MT support: yes, with the standard caveats every ADS-compatible engine has.
- The ABI surface is thread-safe — global registry protected by a recursive mutex; per-thread error
state via thread_local.
- 1 ADSHANDLE per thread is the recommended pattern.
Don't share a single connection / table / index handle across threads without your own external
synchronisation.
- Record / table locks go through LockMgr matching ADS semantics.
- Wire client serialises requests on a single RemoteConnection; for real parallelism over tcp://,
each thread should call AdsConnect60 itself.
There's a multi-threaded stress harness at tools/stress/openads_concurrency_stress that spawns
N workers, each with its own connection, doing concurrent append + lock + read against a shared DBF.
Server: openads_serverd (Windows/Linux/macOS binaries in every release). Speaks an OpenADS-native TCP wire
protocol; clients connect via:
AdsConnect60("tcp://host:port/data_dir", ...)
The same ace64.dll / ace32.dll / libace64.so / libace64.dylib also runs as LocalServer (in-process
DLL, no daemon needed) selected via:
AdsConnect60(path, ADS_LOCAL_SERVER, ...)
MT support: yes, with the standard caveats every ADS-compatible engine has.
- The ABI surface is thread-safe — global registry protected by a recursive mutex; per-thread error
state via thread_local.
- 1 ADSHANDLE per thread is the recommended pattern.
Don't share a single connection / table / index handle across threads without your own external
synchronisation.
- Record / table locks go through LockMgr matching ADS semantics.
- Wire client serialises requests on a single RemoteConnection; for real parallelism over tcp://,
each thread should call AdsConnect60 itself.
There's a multi-threaded stress harness at tools/stress/openads_concurrency_stress that spawns
N workers, each with its own connection, doing concurrent append + lock + read against a shared DBF.
best regards
El sáb, 9 may 2026 a las 15:55, <harbou...@googlegroups.com> escribió:
- Announcing OpenADS - 1 Update
bedipr...@gmail.com <bedipr...@gmail.com>: May 08 12:22PM -0700
Hi Antonio
I am curious about the term used as OpenADS so pinging here
Does it implement SERVER side also ?
If yes, does it support MT applications ?
Pritpal Bedi
a student of software ...more
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to harbour-user...@googlegroups.com.
Antonio Linares
www.fivetechsoft.com
www.fivetechsoft.com
Reply all
Reply to author
Forward
0 new messages