• Post Reply Bookmark Topic Watch Topic
  • New Topic

creating concurrent server using separate threads??

 
james sinclair
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
here is my code but how do i execute that does anyone know?

 
Paul Sturrock
Bartender
Posts: 10336
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Not sure I follow, are you asking us how to run your own code? The normal route would be to call your class by running java. Or is there more to your question?
 
james sinclair
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
sorry i need to know how to. create a cooncurrent server using separate threas for each processing each client request??
 
james sinclair
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
sorry bad spelling!! LOL
i need to know how to create a concurrent server using separate threads for each processing each client request??
 
james sinclair
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
ok ok i have got a bit further i think i have created a concurrent server.. can someone tell me if this is correct.. my next tasks are :

2. It will use a log file to record all transactions. The program
should append to the file and not recreate it if it already exists
(use the Java API documentation to discover how). There
should only be one line per transaction. You should decide what
information is most relevant, however it should include the current
data and time and the client’s IP address (use getInetAddress()).
You can always look at Apache log files to see what
they contain.

3. It will check the resource name (from the first line of the client
request) to see that it starts with a “/” and if not it will return a
400 response.

4. It will correctly deal with HTTP requests GET and HEAD, if
correct, but will return a 501 response if the request is not either
HEAD or GET.

5. It deals the HEAD requests correctly, read RFC2616 (the standard
for HTTP/1.1).

6. The server should always send a:
Connection: close
option line with every response...

does anyone know how to do these?? heres my code

thanks in advance



 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!