1 |
overview of features, platforms and operation modes supported by the |
2 |
the various language bindings |
3 |
|
4 |
* dimensions |
5 |
|
6 |
The bindings are categorized according to whether they support |
7 |
- client sessions |
8 |
All versions of OpenIsis will (some day) support client sessions. |
9 |
Within the database server, however, they are not used |
10 |
(in order to keep it simple, safe and responsive). |
11 |
Where client sessions are used, one can always use |
12 |
multiple client sessions to connect to several servers. |
13 |
multiple sessions from one IP to the same server |
14 |
may or may not be allowed by the server. |
15 |
- multiple threads |
16 |
This is useful only where multiple users are served, |
17 |
i.e. in the server and within a Java Servlet Engine. |
18 |
Multithreaded database access also requires the use |
19 |
of server sessions. |
20 |
- asynchronous operation |
21 |
This is useful only for applications build around an event loop, |
22 |
actually the server and the Tcl/Tk GUI. |
23 |
Of course any asynchronous connection can be easily used synchronous. |
24 |
Asynchronous processing is supported only on a communication channel, |
25 |
i.e. when accessing a remote database. |
26 |
- charset support |
27 |
While any version of OpenIsis will handle any ASCII compatible encoding |
28 |
(including UTF-8) transparently, only Tcl and Java have built-in support |
29 |
for converting charsets. |
30 |
|
31 |
|
32 |
* tabular overview |
33 |
|
34 |
Here, "openisis" denotes the command line utility |
35 |
and server is the openisis server process. |
36 |
|
37 |
| *system* | *client* | *threads* | *async* | *charsets* | |
38 |
| Perl | yes | no | no | no | |
39 |
| Java | yes | yes | no | yes | |
40 |
| Tcl/Tk | yes | no | yes | yes | |
41 |
| openisis | yes | no | no | planned | |
42 |
| C-API | yes | yes | yes | planned | |
43 |
| server | no | yes | yes | planned | |
44 |
|
45 |
|
46 |
* notes |
47 |
|
48 |
- The Tcl/Tk binding (and thus, of course, the C-API) |
49 |
is the only one actively supported for windows. |
50 |
While Perl and Java should work, we won't bother. |
51 |
- Where a Tcl/Tk GUI wishes to operate asynchronously |
52 |
on a local database, it should start a server process. |
53 |
- Neither Perl nor Tcl are meant to be used in a multiuser environment. |
54 |
|
55 |
--- |
56 |
$Id: Bindings.txt,v 1.3 2003/06/02 09:54:14 kripke Exp $ |