Koen, Thanks for explanation! Indeed, there is no need to change server-push-timeout. I believe it became obsolete sometime through WebSockets. :-)
2010/12/13 Koen Deforche <[email protected]> > Dmitriy, > > 2010/12/13 Dmitriy Igrishin <[email protected]>: > > Hey Koen, > > > > So, server-push-timeout has no effect on WebSocket sessions > > altogether ? > > It does, server-push-timeout is still used, but it does not generate a > new request, it simply sends a keep-alive ping/pong over the > websockets (future versions of the WebSockets protocol promise to have > built-in support for these kind of control messages). The application > is not aware of this, unlike for the Ajax-based serverpush. > > Regards, > koen > > > ------------------------------------------------------------------------------ > Oracle to DB2 Conversion Guide: Learn learn about native support for > PL/SQL, > new data types, scalar functions, improved concurrency, built-in packages, > OCI, SQL*Plus, data movement tools, best practices and more. > http://p.sf.net/sfu/oracle-sfdev2dev > _______________________________________________ > witty-interest mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/witty-interest > -- // Dmitriy.
------------------------------------------------------------------------------ Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL, new data types, scalar functions, improved concurrency, built-in packages, OCI, SQL*Plus, data movement tools, best practices and more. http://p.sf.net/sfu/oracle-sfdev2dev
_______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
