|
A wait queue could be an object that: - has a maximum number of active threads (say 50) - accepts an incomming/outgoing communication request, 'translates' this request to a new Thread to be launched - whenever the number of active threads < maximum the new thread is launched using a tcp/ip port - whenever the number of active threads = maximum the new thread is added to a fifo-queue of objects until an active thread ends - when each communication thread is terminating this is signalled to the queue resulting in starting a the first thread on the wait queue (if there's one) ... p.s. isn't jdk1.4 already available as an PTF on the iSeries? Geert (I'm off for the weekend) -----Original Message----- From: Price, Chris [mailto:chris_price@nsb.co.uk] Sent: vendredi 12 avril 2002 14:39 To: 'java400-l@midrange.com' Subject: RE: Communication between JVM's This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Geert, SocketChannel looks interesting, but it could be a long wait before JDK1.4 becomes available on the iSeries....(vbg) What is a wait queue - do you know of any example / documentation anywhere. I am concerned about response times - ideally the servlet that generates message should wait for acknowledgement from the client that it has received it before continuing, so a error page can be displayed if necessary. I'm still in the early design stages, so any suggestion for better ways will be welcomed. Chris. -----Original Message----- From: Geert Van Landeghem [mailto:gvl@reynderseti.be] Sent: 12 April 2002 15:24 To: 'java400-l@midrange.com' Subject: RE: Communication between JVM's How long do you estimate the duration of the communication? Have a look at the new Channel classes that allow non-blocking input from files, sockets, ... perhaps this will benefit you. I see no difference using sockets to communicate between two JVM's either on different machines or on the same machine. If you're afraid of to many socket communications and response time is not a problem you could implement a wait queue which allows only a maximum number of socket communications to be active. Hope this helps. Geert -----Original Message----- From: Price, Chris [mailto:chris_price@nsb.co.uk] Sent: vendredi 12 avril 2002 14:08 To: 'java400-l@midrange.com' Subject: RE: Communication between JVM's This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] It's kind of a messaging system. My WAS needs to sends messages to some clients, via a router. The router to client part I'm happy to be socket based. If the WAS & the router are running on different machines, then they will have to use sockets to communicate. BUT if they are the same machine, will it be inefficient to communicate via sockets? I'm also nervous about large number of sockets being opened in the WAS, as each one is going to tie-up a TCP/IP port for the duration of the conversation. Chris. -----Original Message----- From: Geert Van Landeghem [mailto:gvl@reynderseti.be] Sent: 12 April 2002 15:01 To: 'java400-l@midrange.com' Subject: RE: Communication between JVM's In my humble opinion, no. You could use File objects on disk, an OODBMS, ... to share information. The most low level communication is always done by using sockets. What kind of application do you want to write? Geert -----Original Message----- From: Price, Chris [mailto:chris_price@nsb.co.uk] Sent: vendredi 12 avril 2002 13:51 To: 'java400-l@midrange.com' Subject: RE: Communication between JVM's This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Are there no more efficient solutions than sockets (which all these ultimately use)? -----Original Message----- From: Geert Van Landeghem [mailto:gvl@reynderseti.be] Sent: 12 April 2002 14:45 To: 'java400-l@midrange.com' Subject: RE: Communication between JVM's There are several possibilities using: - sockets - RMI or Remote Method Invocation (serialized objects over sockets) - EJB (Application server) to clients - Servlet/JSP (Application Server) to clients ... Geert -----Original Message----- From: Price, Chris [mailto:chris_price@nsb.co.uk] Sent: vendredi 12 avril 2002 13:25 To: 'java400-l@midrange.com' Subject: Communication between JVM's This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] All, What is the best way of communicating between two different JVM's, running on the same machine? Chris. _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l. _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l. _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l. _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l. _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l. _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l. _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.