[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Non Threaded use of TCPSocket with select/poll?
From: |
Federico Montesino Pouzols |
Subject: |
Re: Non Threaded use of TCPSocket with select/poll? |
Date: |
Tue, 7 Jan 2003 12:27:19 +0100 |
User-agent: |
Mutt/1.4i |
Yes, I would say that with CC++ you need to create at least one
additional thread.
On Mon, Jan 06, 2003 at 04:33:49PM +0000, Jeremy Noetzelman wrote:
> My point is I want a single thread for the entire application. Not two,
> not more than two. One. It doesn't seem that CommonC++ supports such an
> application without a fair amount of work. Please correct me if I'm wrong
> though.
>
> J
>
> On Mon, 6 Jan 2003, Federico Montesino Pouzols wrote:
>
> >
> > If you only want a limited number of threads and to simulate
> > concurrency through select/poll, I think the SocketPort and
> > SocketService classes are the most adequate classes in Common
> > C++. There is a tcpservice demo that shows how to use them.
> >
> > On Fri, Jan 03, 2003 at 08:26:11PM +0000, Jeremy Noetzelman wrote:
> > > I'm more concerned about having a proper select polling loop for the
> > > server socket ... I'm less concerned about the client connection sockets.
> > >
> > > On Fri, 3 Jan 2003, Albert Strasheim wrote:
> > >
> > > > Hello,
> > > >
> > > > >From the Common C++ documentation for tcpstream (not TCPStream):
> > > >
> > > > A more natural C++ "tcpstream" class for use by non-threaded
> > > > applications. C++ "fstream" style tcpstream class.
> > > >
> > > > I don't know if this is what you want?
> > > >
> > > > Cheers,
> > > >
> > > > Albert
> > > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Bug-commoncpp mailing list
> > > address@hidden
> > > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> >
>