Salvatore, > Are you sure that most applications don't need System.Messaging ?
We use it for queuing messaging about train delays for an application distributed all around Italy in hundreds of clients (about 10 clients in the average for each italian railway station). As you can imagine, Message Queuing is important to be used in such these kind of contexts: I don't see how an application running on a single machine could make a use of such that architecture. Anyway, remember System.Messaging implements just Message Queuing system: this doesn't mean it includes net protocols for messaging (like SMTP, POP3, XMMP or other protocols). Cheers. Antonello On 12/13/06, laas <[EMAIL PROTECTED]> wrote: > On 12/13/06, Miguel de Icaza <[EMAIL PROTECTED]> wrote: > > > So you were thinking of "Instant Messaging" and not messaging along > > the lines of COM+. You could have saved yourself a lot of time had you > > googled what you were looking for. > > > > Most applications out there do not need System.Messaging, you just > > got the terms confused. > > > > > > > > Are you sure that most applications don't need System.Messaging ? > however, thanks for your answer ! > > Regards, > > -- > [LAAS] > aka Salvatore > WebSite: http://laas.altervista.org > YTSite: http://laas.altervista.org/youtranslate/ytindex.php > _______________________________________________ > Mono-list maillist - [email protected] > http://lists.ximian.com/mailman/listinfo/mono-list > > > _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
