My French is non-existant but babelfish managed to get some meaning out of your comments. It seems to me that there is a little confusion about the technical basis of Brutus, so I'll try to clarify that in a few words. I'll hope you'll forgive me for keeping this post entirely in English.
Brutus is technically speaking a CORBA wrapper that wraps native MAPI in a large set of appropiately defined CORBA methods and types. It is therefore a requirement that the Brutus server part is installed on some Windows server where the correct version of the MAPI dll is located. The Exchange server itself is the supported choice.
The Brutus IDL files, on the other hand, makes it possible for *any* client to connect to Brutus, and thereby Exchange, as long as some CORBA implementation is available on the client box.
The primary goal of Brutus is to enable any client to integrate into an Exchange infrastructure on an equal footing with Outlook.
# In short..
Posté par colding . En réponse à la dépêche Enfin un connecteur Linux pour Microsoft Exchange 5.5. Évalué à 10.
My French is non-existant but babelfish managed to get some meaning out of your comments. It seems to me that there is a little confusion about the technical basis of Brutus, so I'll try to clarify that in a few words. I'll hope you'll forgive me for keeping this post entirely in English.
Brutus is technically speaking a CORBA wrapper that wraps native MAPI in a large set of appropiately defined CORBA methods and types. It is therefore a requirement that the Brutus server part is installed on some Windows server where the correct version of the MAPI dll is located. The Exchange server itself is the supported choice.
The Brutus IDL files, on the other hand, makes it possible for *any* client to connect to Brutus, and thereby Exchange, as long as some CORBA implementation is available on the client box.
The primary goal of Brutus is to enable any client to integrate into an Exchange infrastructure on an equal footing with Outlook.
Best regards,
jules (www.omesc.com)