OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: ODF 1.2 draft 4 comment: Generic mechanism for storing interprocess communication parameters

Currently only one platform-dependent, legacy API for interprocess 
communication is described in the specification, in 14.7 (DDE Connections). 

(Microsoft states about DDE "DDE is not as efficient as newer technologies." 

Also, users of ODF applications on many platforms have no way to legitimately 
embed information their api's need, including popular cross-platform 
technologies like DBUS [1]. Online ODF editors that function e.g. in the 
browser or as a remote service will also need other technologies than provided 
by DDE. 

There should be a generic way to identify IPC api's, and the parameters needed 
to successfully establish a working interprocess communication. Ideally, OASIS 
would maintain a public register allowing for the registration of api's and 
their syntax, so that application vendors can create more robust solutions in 
this area by putting in fallback mechanism for connections like is done with 
frames (if dbus fails, try dde etc).

Michiel Leenaars
NLnet foundation

[1] http://www.freedesktop.org/wiki/Software/dbus

This is a digitally signed message part.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]