Service is Mono as well as we wanted maximal portability. Also, can you post those init differences? I don't want to be stepping on same rakes...
V. Amc Gmail wrote: > We are using simple .NET Remoting with tcp channel and that works > nicely under both MS.NET and Mono. Only the initialization is slightly > different, but it's one line of code under #ifdef. > In other projects we have sockets or WebRequest/WebResponse exchange, > which you may also consider if your service is not a .NET-based but > rather plain c/c++ I did not personally test those on Mono but pretty > sure it's OK. > -- amc > > > On 11/2/07, Robert Jordan <[EMAIL PROTECTED]> wrote: > >> Vasili Sviridov wrote: >> >>> Hello all, >>> >>> I have a service which performs TCP/IP data exchange with multiple clients. >>> I also have a web page, on which I'd like to have a "ping" button, that >>> should tell the service to send a certain packet to the client and >>> return a response. >>> >>> My question is - what's the best way to implement this? >>> I've found an implementation of named pipes by Ivan Latunov, but it >>> looks like its windows only. Currently that's OK, but i know for sure >>> that the project will be moved to linux entirely. >>> >>> Is there an implementation that's lightweight and works on both runtimes? >>> >> You could use .NET Remoting with IPC channels. That's .NET 2.0 only, >> though. See System.Runtime.Remoting.IpcChannel on MSDN. >> >> OTOH, since you already have a TCP/IP service, why don't you access >> it via localhost? >> >> Robert >> >> _______________________________________________ >> 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 > _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
