----- Original Message ----- From: "Dean Michael Berris" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, March 31, 2003 12:15 PM Subject: Re: [plug] Re: unified way of data exchange
> On Mon, 2003-03-31 at 11:01, fooler wrote: > > > is there a way for 2 (or more) completely different and unrelated > > > applications to be able to exchange persistent information (i.e. data, > > > objects) via some channel/server? > > > > yes thru InterProcess Communication (IPC)... you have lots of choices here > > and these are the followings: > > persistence is what i am after though. IPC is a method just for > communication, no means for letting the communication or the data in > transit to be stored somehow for some future reference of >1 > application(s). IPC mechanisms are used to support distributed processing... its up to you to provide persistence on a low level programming :-> > and besides, this works for *nixes. i'm not sure if other OSes > have/support IPC. anyone that knows whether it could be done in Windows? > please let me know... =) i thought that you are only focusing on unix environment because windows is a different animal thing :-> but if you want both for windows and all unix major platform, i believe Distributed Component Object Model (DCOM) is best suited for you... DCOM is no longer proprietary to microsoft :-> but if you dont like DCOM then socket network programming is your last option... > > > socket programming is too OS specific and too much a burden for an > > > application to incorporate into it consciously. > > > > because you are afraid to start working on it :-> socket programming is not > > too OS specific... BSD socket is the de facto standard for socket > > programming.. use it and your code is portable to other OSes... > > > > ahem... i am not afraid to start working on it. i _am_ working on it > now, and i agree, it's not hard. what i meant was, that if i was > programming an application and consciously incorporating it into the app > could be a hassle. i mean, i should care less on creating a socket > connection to a database management system, then manually having to use > the low level send() and recv() methods -- there are API's already for > that so that you could use them to do just what you want. unless of > course you wanna do it the less easier way... ;) then why not create your own API with these low level functions so that you have full control over it? :-> so that for easy integration for your future work :-> fooler. _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
