Hi Brad,
> -----Original Message-----
> From: Brad Clements [mailto:[EMAIL PROTECTED]]
> Sent: Freitag, 1. Februar 2002 23:37
> To: [EMAIL PROTECTED]
> Subject: Porting to Novell NetWare
>
>
> Any interest in a port to Novell NetWare?
>
Do you know any open source project, that is not interested in other ports
as long as it does not produce too much extra efforts ;-)
>
> --
>
> What kind of memory requirements does the kernel have?
>
It uses shared memory for communication and for monitoring console
activities. The amount of memory strongly depends on parameters for
CACHESIZE.
>
> What kind of threading is used (thread groups, thread local
> storage, etc)
>
User tasks are organizied in thread groups bases on POSIX pthreads
respectively Fibers on WIN32 (to keep at most one active thread per avalable
CPU). Thread local storage is used to find task control structures only
(that is only one well known TLS key needed...)
>
> What kind of disk I/O (raw disks, standard C files, etc)
>
Raw disk I/O is not a must. Standard file should always be supported.
ReadOnly files are not suppored yet.
> --
>
> Is there C++ in the source code (sorry haven't looked). If
> yes, are exceptions, RTTI
> used? (not available on NetWare)
All new stuff is C++ coding.
Exceptions yes (unfortunatly since they got a bad reputation due to lots of
compiler features...)
RTTI currently forbidden - when coding startet on AIX there was just CSet++
and we uses the minimum feature set (i.e. no <dynamic_cast>...). Anyhow it
would increase the size of EACH class instance, even those that do not need
RTTI at all...
>
> --
>
> For the C client library. Is multi-threading supported (win32, linux)?
Yes for ODBC it is used, but the runtime calls are serialized by an
extrernal mutex.
>
> What's the story with "8 connections per user" Is that 8 per
> client process, or really only
> 8 connections from "sysdba" or otherwise?
Here is your story:
The number of CONCURRENT connection from ONE client up to 7.3.0 Build 20 on
UNIX is limited to 8.
This was a bug, that is fixed only now (7.3.0 Build 21 PTS 1113724). There
was a dynamic allocation of connection slots in the client runtime, which
began with an 8 connection chunk and never growed... No problem for R/3
since work processes limited concurrent connections to 8 and precompiler not
too long ago also limited number of connection to 8 (why not 42?). But
detected by each application that was trying to establish more than 8
concurrent connections.
Since R/3 uses parallel working work processes with max. 8 connections each,
the number of users of R/3 systems
have not been limited, but recently somebody tried to monitor more that 8
databases using a single monitor application and he ran into that problem.
This was a bug in the UNIX client runtime only, so number of connection from
WIN is unlimited anyhow.
For those eagerly waiting for it, here is the patch modification....
Line 733 in sys/src/en/ven03.c:
/*
* Select a reference number.
*/
>>>>>
ref = sql03_alloc_connect (); /* PTS 1113724 fixed wrong limitation to
maximum of 8 connections */
<<<<<
ref = sql03_find_free_index ();
By the way, Potsdam bei Berlin,Germany is not that fare away ;-)
CU
jrg
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
