| |
browse.develop.com
Browse.develop.com is a community that was established to collect and
organize valuable web information. Our technical staff have selected and
indexed information and courses that they feel will help you stay
current on best practices across the SDLC.
|
16 Articles match "Server Side","Web"
| Related DevelopMentor Courses | MORE | | Using SignalR for real time communication on the web Unfortunately the current support for WebSockets, both on the client and on the server, is still somewhat limited making this a thing of the future. SignalR to the resque Even if a pure Web Socket solution isn’t possible yet there are perfectly good alternatives. So if SignalR works today does it mean it doesn’t use Web Sockets? And depending on the client and sever capabilities it can use one or 4 different networking techniques WebSockets Server Send Events Forever frame Long polling It just chooses the best solution that both the browser and server support. The Problem Solver - Monday, July 9, 2012 Guerrilla.NET (UK) Training Write modern web applications that are simpler to unit test with ASP.NET MVC. How do I take advantage of the latest innovations in web development? How can I build web applications and services that use claims based authorization? ASP.NET has used server sided controls to build "web forms". This new approach is called ASP.NET MVC and creates code that is much easier to unit test than web forms and so lends itself well to Test Driven Development. Leverage new features of C# 4.0, including named and optional parameters and dynamic typing. couldn't? DevelopMentor Courses - Tuesday, March 1, 2011 HTML5 WebSockets One of the most exiting new things in HTML5 is the ability to start pushing data from the server to the client. Traditionally web applications have depended on clients requesting data from the server. The long polling mechanism has actually been formalized in the HTML5 specs as well with Server-sent DOM events and the the EventSource object. Where the EventSource object uses standard HTTP traffic and has no special requirements on the server the same isn’t true for WebSockets. The most popular server side implementation seems to be Socket.IO The Problem Solver - Thursday, July 5, 2012 |
10 Articles match "Server Side","Web"
| The Latest from DevelopMentor | MORE | | Using SignalR for real time communication on the web Unfortunately the current support for WebSockets, both on the client and on the server, is still somewhat limited making this a thing of the future. SignalR to the resque Even if a pure Web Socket solution isn’t possible yet there are perfectly good alternatives. So if SignalR works today does it mean it doesn’t use Web Sockets? And depending on the client and sever capabilities it can use one or 4 different networking techniques WebSockets Server Send Events Forever frame Long polling It just chooses the best solution that both the browser and server support. The Problem Solver - Monday, July 9, 2012 Using SignalR for real time communication on the web Unfortunately the current support for WebSockets, both on the client and on the server, is still somewhat limited making this a thing of the future. SignalR to the resque Even if a pure Web Socket solution isn’t possible yet there are perfectly good alternatives. So if SignalR works today does it mean it doesn’t use Web Sockets? And depending on the client and sever capabilities it can use one or 4 different networking techniques WebSockets Server Send Events Forever frame Long polling It just chooses the best solution that both the browser and server support. The Problem Solver - Monday, July 9, 2012 HTML5 WebSockets One of the most exiting new things in HTML5 is the ability to start pushing data from the server to the client. Traditionally web applications have depended on clients requesting data from the server. The long polling mechanism has actually been formalized in the HTML5 specs as well with Server-sent DOM events and the the EventSource object. Where the EventSource object uses standard HTTP traffic and has no special requirements on the server the same isn’t true for WebSockets. The most popular server side implementation seems to be Socket.IO The Problem Solver - Thursday, July 5, 2012 | -
| The Best from DevelopMentor | MORE | - Using SignalR for real time communication on the web
Unfortunately the current support for WebSockets, both on the client and on the server, is still somewhat limited making this a thing of the future. SignalR to the resque Even if a pure Web Socket solution isn’t possible yet there are perfectly good alternatives. So if SignalR works today does it mean it doesn’t use Web Sockets? And depending on the client and sever capabilities it can use one or 4 different networking techniques WebSockets Server Send Events Forever frame Long polling It just chooses the best solution that both the browser and server support. The Problem Solver - Monday, July 9, 2012 - Replacing ASP.NET Forms Authentication with WIF Session Authentication (for the better)
Supports server side caching (which is an extensible mechanism). Has an extensible mechanism for protection (DPAPI by default, RSA as an option for web farms, and machine key based protection is coming in.NET 4.5). Implements caching of the principal on the server side (aka session mode) if configured in an AppSetting. Very useful if you are implementing services or web APIs where you want the actual status code to be preserved. The main difference between the two is the identity to cookie serialization engine that sits below. But that’s easy to add ;). www.leastprivilege.com - Thursday, February 9, 2012 - HTML5 WebSockets
One of the most exiting new things in HTML5 is the ability to start pushing data from the server to the client. Traditionally web applications have depended on clients requesting data from the server. The long polling mechanism has actually been formalized in the HTML5 specs as well with Server-sent DOM events and the the EventSource object. Where the EventSource object uses standard HTTP traffic and has no special requirements on the server the same isn’t true for WebSockets. The most popular server side implementation seems to be Socket.IO The Problem Solver - Thursday, July 5, 2012 - Protecting Cookies: Once and For All
Every once in a while you run into a situation where you need to temporarily store data for a user in a web app. You typically have two options here – either store server-side or put the data into a cookie (if size permits). When you need web farm compatibility in addition – things become a little bit more complicated because the data needs to be available on all nodes. transforms; private ChunkedCookieHandler _handler = new ChunkedCookieHandler (); // DPAPI protection (single server). In my case I went for a cookie – but I had some requirements. private List. www.leastprivilege.com - Tuesday, May 31, 2011 - HTML5 WebSockets
One of the most exiting new things in HTML5 is the ability to start pushing data from the server to the client. Traditionally web applications have depended on clients requesting data from the server. The long polling mechanism has actually been formalized in the HTML5 specs as well with Server-sent DOM events and the the EventSource object. Where the EventSource object uses standard HTTP traffic and has no special requirements on the server the same isn’t true for WebSockets. The most popular server side implementation seems to be Socket.IO The Problem Solver - Thursday, July 5, 2012 - Using SignalR for real time communication on the web
Unfortunately the current support for WebSockets, both on the client and on the server, is still somewhat limited making this a thing of the future. SignalR to the resque Even if a pure Web Socket solution isn’t possible yet there are perfectly good alternatives. So if SignalR works today does it mean it doesn’t use Web Sockets? And depending on the client and sever capabilities it can use one or 4 different networking techniques WebSockets Server Send Events Forever frame Long polling It just chooses the best solution that both the browser and server support. The Problem Solver - Monday, July 9, 2012 - Fix for WordPress XMLRPC 500 Internal Server Error
was getting a 500 Internal Server Error. enabled Failed Request Tracing in IIS7 to find out what was happening server-side to cause the HTTP 500 error. did it at the command line on my 64-bit Windows server: cd "C:Program Files (x86)MySQLMySQL Server 5.1bin" mysql.exe –u root -p Enter password: **. I’m going to go out on a limb here and assume that you can figure out how to run mysql on Linux if you’re running your own Linux server. was able to fix the problem by making a small change to the database. The Error Message. at the time). Ardent Dev - Wednesday, July 15, 2009 %>
| |   |
