Ernesto I prefer to have all my URL mappings centralized, so I try to use
the Wicket way where available. Although it's interesting to know that you
can access wicket Session this way.

What I'd really do is try to proxy/tunnel the stream directly from the
webcam to the client using an appropriate format once I've checked the
request is from an identified client. This would be the most memory
efficient way.
I suppose that if the webcam offers some kind of streamable video format
 (instead of buffered images), you could forward the response output from
the webcam to the client. This way the client would make a single request
to your wicket server and cpu and memory usage would be minimized.

Marc Nuri

On Mon, Jan 14, 2013 at 10:30 AM, Decebal Suiu <> wrote:

> Hi Marc
> Thanks for response. A custom Mapper with a RequestHandler that do my job
> was one of ideas but onRespond I must implement a while loop and I know if
> it's ok.
> For example:
> public void respond(IRequestCycle requestCycle) {
>    // se content type to "multipart/x-mixed-replace;boundary=myboundry"
>    // set no cache
>    // send grab images
>     while (!stop) {
>         // send next images
>         // sleep some milliseconds related to FPS (frames on second)
>     }
> }
> A solution is to use an external servlet that handles request related to
> webcam or a wicket push technic.
> For me, wicket is a (nice) hammer on web development and the problem is
> that
> I intend to resolve all problems this hammer :)
> Best regards,
> Decebal
> --
> View this message in context:
> Sent from the Users forum mailing list archive at
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Reply via email to