Hey Marco, 2011/12/21 Marco Faletra <m.fale...@gmail.com>: > @Koen > With CORS the responsefrom video server is "404 Error": so it > doesn't support "OPTIONS", I think.
OPTIONS are however only used in CORS if you use POST. With a GET request there should not be such a response ? > Do you know how to make a simple proxy from Wt server vs browser? So > the browser do the worst of work. That would involve a custom WResource which uses the HTTP client. Now that I think of it, this could be a generally useful addition (now that we have the HTTP client since 3.2.0). > What do you mean with: "When you refresh a resource, like you do > below, only the image is updated though, not the whole page ?" > Maybe I repeat but what I see is that every time an image is arrive > I do "m_imageResource->setData (inStream_);" but the image on browser > is not refresh. > I have to write "Wt::WApplication::instance()->triggerUpdate();" to > take a semi-normal refresh. As I said, your code wasn't entirely correct -- it seems that you did not enable server push ? Take a look at the server push feature example. Regards, koen ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ witty-interest mailing list witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest
