Re: [Simpleweb-Support] Outputing MJPEG

[<nia...@rb...>]

I would say create the server to use only a small amount of threads then hand off the task to a separate thread like so.

public void handle(final Request req, final Response resp) {
   threadPool.execute(new Runnable() {
      public void run() {
         try {
            streamVideo(req, resp);
            resp.close();
         } catch(Exception e) { 
            log.report(e);
         }
      }
   });
}

Here you ensure that regardless of the number of threads being used by the server, you can handle any number of live video streams by providing a thread pool to service the streams.

Niall Gallagher
RBS Global Banking & Markets
Office: +44 2070851454   

-----Original Message-----
From: Farhad [mailto:xa...@gm...] 
Sent: 08 July 2010 10:42
To: Simple support and user issues
Subject: Re: [Simpleweb-Support] Outputing MJPEG

Thanks might, that worked like a charm.

The client is a standard web browser.

I wonder though, is it ok to use the same thread created by Simple to do the output, since it will get busy for a long time.

Thanks

7 jul 2010 kl. 18.00 skrev <nia...@rb...> <nia...@rb...>:

> 
> What is the client? Is it a HTTP client? If you do not specify a content length the Simple will send it as chunked encoded which a HTTP/1.1 client should be able to support. 
> 
> If you want no processing then you can set to connection close semantics like so.
> 
> resp.set("Connection", close")
> 
> This will mean there is no modification of the response, and the connection is closed only if you invoke the OutputStream.close().
> 
> 
> 
> Niall Gallagher
> RBS Global Banking & Markets
> Office: +44 2070851454   
> 
> -----Original Message-----
> From: Farhad [mailto:xa...@gm...]
> Sent: 07 July 2010 12:07
> To: sim...@li...
> Subject: [Simpleweb-Support] Outputing MJPEG
> 
> Hi,
> 
> We would like to use Simple to receive a HTTP request with a Container and extract the OutputStream, which we then use to output a live multipart MJPG video stream.
> 
> When this is done using a plain java ServerSocket the browser has no problem with displaying the video. However this is not the case when using Simple.
> 
> Obviously Simple parses the output and modifies it according to HTTP standards. Is there a way to get the actual socket outputstream in a Container (and possibly pass it over to another thread) and then prevent Simple from closing it or processing it?
> 
> Thanks
> ----------------------------------------------------------------------
> -------- This SF.net email is sponsored by Sprint What will you do 
> first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Simpleweb-Support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpleweb-support
> 
> **********************************************************************
> ************* The Royal Bank of Scotland plc. Registered in Scotland 
> No 90312.
> Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. 
> Authorised and regulated by the Financial Services Authority. The 
> Royal Bank of Scotland N.V. is authorised and regulated by the De 
> Nederlandsche Bank and has its seat at Amsterdam, the Netherlands, and 
> is registered in the Commercial Register under number 33002587. 
> Registered Office: Gustav Mahlerlaan 10, Amsterdam, The Netherlands. 
> The Royal Bank of Scotland N.V. and The Royal Bank of Scotland plc are 
> authorised to act as agent for each other in certain jurisdictions.
> 
> This e-mail message is confidential and for use by the addressee only.
> If the message is received by anyone other than the addressee, please 
> return the message to the sender by replying to it and then delete the 
> message from your computer. Internet e-mails are not necessarily 
> secure. The Royal Bank of Scotland plc and The Royal Bank of Scotland 
> N.V. including its affiliates ("RBS group") does not accept 
> responsibility for changes made to this message after it was sent.
> 
> Whilst all reasonable care has been taken to avoid the transmission of 
> viruses, it is the responsibility of the recipient to ensure that the 
> onward transmission, opening or use of this message and any 
> attachments will not adversely affect its systems or data. No 
> responsibility is accepted by the RBS group in this regard and the 
> recipient should carry out such virus and other checks as it considers appropriate.
> 
> Visit our website at www.rbs.com
> 
> **********************************************************************
> *************
> 
> 
> ----------------------------------------------------------------------
> -------- This SF.net email is sponsored by Sprint What will you do 
> first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Simpleweb-Support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpleweb-support


------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Simpleweb-Support mailing list
Sim...@li...
https://lists.sourceforge.net/lists/listinfo/simpleweb-support