Comments on: Authenticated web services calls with Asp.Net MVC

By: Viky

Viky — Tue, 16 Feb 2010 04:20:53 +0000

Good one

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 15:54:45 +0000

@JC Grubbs: at worst it would result in 2 calls for every request. But for my application, I tend to see a lot of calls in bursts. That is why I do a time check on my call.

Now, as for sending redefined JSON objects…I’m not sure I could do that without doing a LOT of extra work, especially for Load calls (which recieve HTML, not JSON). Plus, most of my get calls are already returning a lot of data. In fact, that is what half of my XHR calls are for — return data to the browse.

By: JC Grubbs

JC Grubbs — Tue, 08 Dec 2009 15:18:59 +0000

Wouldn’t this result in making two XHR calls for every request…one for the authentication check and another for the “real” request? Another option is to turn off Forms Authentication for all your web service URLs and then use a re-invention of the [Authorize] filter on those action methods that doesn’t redirect back to Login but instead sends some predefined JSON object indicating that the user is not authenticated or allows the actual method to be called. This results in a single XHR call and allows you to just handle the special authentication value in the direct jQuery method instead of wrapping it.

By: John Sonmez

John Sonmez — Tue, 08 Dec 2009 00:46:19 +0000

@Chris Brandsma Oops sorry, I wasn't clear enough. I meant the wrapped JQuery calls, but I suppose that is not a huge amount of overhead.

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 00:39:30 +0000

Hi guys,

Good suggestions all rounds. Pretty much proves I should have spent a little more time on the post. But I’ll look into what Sergio and Ben were talking about.

But a few things:
@John Sonmez: You shouldn’t have to write it for every page. Put the code in a js file and load it in a master page.

@Bill Pierce: Keeping the session alive is only a temporary fix. Do you keep it alive all night? All weekend? Each session is taking server resources. At some point you have to let the session die and move on. The other option is to abuse setInterval.

By: Sergio Pereira

Sergio Pereira — Mon, 07 Dec 2009 16:37:24 +0000

I try to avoid wrapping the jQuery calls if possible. Wrapping jQuery ajax means you’ll have problems with 3rd party plugins that use them.
As Mike suggested, I normally use the jQuery ajaxError event to detect a session expired and force a page reload (which will take me to the login page and redirect me back to the right place when I’m done).
For that to work I make my login page return an HTTP status code like 401-Unauthorized and check for that in the ajaxError event.

By: Bill Pierce

Bill Pierce — Mon, 07 Dec 2009 16:08:17 +0000

I would have opted for the simpler solution and just keep the user’s session alive as long as they do not navigate away from the site.

http://blechie.com/WPierce/archive/2007/11/26/Session-Keep-Alive-with-MonoRail-and-jQuery.aspx

-Bill

By: John Sonmez

John Sonmez — Mon, 07 Dec 2009 15:10:43 +0000

Hmm… I am wondering if there might be a custom HttpModule solution here that could reduce the code on each page, so that you could write the module once and not have to remember to use the special handling for each page of the application. Don’t get me wrong I like your solution, its a very smart way to handle putting the logic that deals with the login page in one place. The only problem I have is that it still has to be used for every page.

By: Paul Speranza

Paul Speranza — Mon, 07 Dec 2009 13:27:31 +0000

I agree with Mark. I make one call that returns a ServiceCallResult object that has a result property to hold data coming back, a success property and a collection of status/error messages with codes that get populated when success is false to tell me (without details) what is wrong like a session timeout, not authenticated/authorized.

Simple but it works. If anyone has something different or better let’s hear it.

By: Reflective Perspective - Chris Alcock » The Morning Brew #492

Viky — Tue, 16 Feb 2010 04:20:53 +0000

Good one

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 15:54:45 +0000

@JC Grubbs: at worst it would result in 2 calls for every request. But for my application, I tend to see a lot of calls in bursts. That is why I do a time check on my call.

By: JC Grubbs

JC Grubbs — Tue, 08 Dec 2009 15:18:59 +0000

By: John Sonmez

John Sonmez — Tue, 08 Dec 2009 00:46:19 +0000

@Chris Brandsma Oops sorry, I wasn't clear enough. I meant the wrapped JQuery calls, but I suppose that is not a huge amount of overhead.

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 00:39:30 +0000

Hi guys,

Good suggestions all rounds. Pretty much proves I should have spent a little more time on the post. But I’ll look into what Sergio and Ben were talking about.

But a few things:
@John Sonmez: You shouldn’t have to write it for every page. Put the code in a js file and load it in a master page.

By: Sergio Pereira

Sergio Pereira — Mon, 07 Dec 2009 16:37:24 +0000

By: Bill Pierce

Bill Pierce — Mon, 07 Dec 2009 16:08:17 +0000

I would have opted for the simpler solution and just keep the user’s session alive as long as they do not navigate away from the site.

http://blechie.com/WPierce/archive/2007/11/26/Session-Keep-Alive-with-MonoRail-and-jQuery.aspx

-Bill

By: John Sonmez

John Sonmez — Mon, 07 Dec 2009 15:10:43 +0000

By: Paul Speranza

Paul Speranza — Mon, 07 Dec 2009 13:27:31 +0000

Simple but it works. If anyone has something different or better let’s hear it.

By: Reflective Perspective - Chris Alcock » The Morning Brew #492

Viky — Tue, 16 Feb 2010 04:20:53 +0000

Good one

Comments on: Authenticated web services calls with Asp.Net MVC

Viky — Tue, 16 Feb 2010 04:20:53 +0000

Good one

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 15:54:45 +0000

@JC Grubbs: at worst it would result in 2 calls for every request. But for my application, I tend to see a lot of calls in bursts. That is why I do a time check on my call.

By: JC Grubbs

JC Grubbs — Tue, 08 Dec 2009 15:18:59 +0000

By: John Sonmez

John Sonmez — Tue, 08 Dec 2009 00:46:19 +0000

@Chris Brandsma Oops sorry, I wasn't clear enough. I meant the wrapped JQuery calls, but I suppose that is not a huge amount of overhead.

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 00:39:30 +0000

Hi guys,

Good suggestions all rounds. Pretty much proves I should have spent a little more time on the post. But I’ll look into what Sergio and Ben were talking about.

But a few things:
@John Sonmez: You shouldn’t have to write it for every page. Put the code in a js file and load it in a master page.

By: Sergio Pereira

Sergio Pereira — Mon, 07 Dec 2009 16:37:24 +0000

By: Bill Pierce

Bill Pierce — Mon, 07 Dec 2009 16:08:17 +0000

I would have opted for the simpler solution and just keep the user’s session alive as long as they do not navigate away from the site.

http://blechie.com/WPierce/archive/2007/11/26/Session-Keep-Alive-with-MonoRail-and-jQuery.aspx

-Bill

By: John Sonmez

John Sonmez — Mon, 07 Dec 2009 15:10:43 +0000

By: Paul Speranza

Paul Speranza — Mon, 07 Dec 2009 13:27:31 +0000

Simple but it works. If anyone has something different or better let’s hear it.

By: Reflective Perspective - Chris Alcock » The Morning Brew #492

Chris Brandsma — Tue, 08 Dec 2009 15:54:45 +0000

@JC Grubbs: at worst it would result in 2 calls for every request. But for my application, I tend to see a lot of calls in bursts. That is why I do a time check on my call.

Comments on: Authenticated web services calls with Asp.Net MVC

Viky — Tue, 16 Feb 2010 04:20:53 +0000

Good one

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 15:54:45 +0000

@JC Grubbs: at worst it would result in 2 calls for every request. But for my application, I tend to see a lot of calls in bursts. That is why I do a time check on my call.

By: JC Grubbs

JC Grubbs — Tue, 08 Dec 2009 15:18:59 +0000

By: John Sonmez

John Sonmez — Tue, 08 Dec 2009 00:46:19 +0000

@Chris Brandsma Oops sorry, I wasn't clear enough. I meant the wrapped JQuery calls, but I suppose that is not a huge amount of overhead.

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 00:39:30 +0000

Hi guys,

Good suggestions all rounds. Pretty much proves I should have spent a little more time on the post. But I’ll look into what Sergio and Ben were talking about.

But a few things:
@John Sonmez: You shouldn’t have to write it for every page. Put the code in a js file and load it in a master page.

By: Sergio Pereira

Sergio Pereira — Mon, 07 Dec 2009 16:37:24 +0000

By: Bill Pierce

Bill Pierce — Mon, 07 Dec 2009 16:08:17 +0000

I would have opted for the simpler solution and just keep the user’s session alive as long as they do not navigate away from the site.

http://blechie.com/WPierce/archive/2007/11/26/Session-Keep-Alive-with-MonoRail-and-jQuery.aspx

-Bill

By: John Sonmez

John Sonmez — Mon, 07 Dec 2009 15:10:43 +0000

By: Paul Speranza

Paul Speranza — Mon, 07 Dec 2009 13:27:31 +0000

Simple but it works. If anyone has something different or better let’s hear it.

By: Reflective Perspective - Chris Alcock » The Morning Brew #492

JC Grubbs — Tue, 08 Dec 2009 15:18:59 +0000

Comments on: Authenticated web services calls with Asp.Net MVC

Viky — Tue, 16 Feb 2010 04:20:53 +0000

Good one

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 15:54:45 +0000

@JC Grubbs: at worst it would result in 2 calls for every request. But for my application, I tend to see a lot of calls in bursts. That is why I do a time check on my call.

By: JC Grubbs

JC Grubbs — Tue, 08 Dec 2009 15:18:59 +0000

By: John Sonmez

John Sonmez — Tue, 08 Dec 2009 00:46:19 +0000

@Chris Brandsma Oops sorry, I wasn't clear enough. I meant the wrapped JQuery calls, but I suppose that is not a huge amount of overhead.

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 00:39:30 +0000

Hi guys,

Good suggestions all rounds. Pretty much proves I should have spent a little more time on the post. But I’ll look into what Sergio and Ben were talking about.

But a few things:
@John Sonmez: You shouldn’t have to write it for every page. Put the code in a js file and load it in a master page.

By: Sergio Pereira

Sergio Pereira — Mon, 07 Dec 2009 16:37:24 +0000

By: Bill Pierce

Bill Pierce — Mon, 07 Dec 2009 16:08:17 +0000

I would have opted for the simpler solution and just keep the user’s session alive as long as they do not navigate away from the site.

http://blechie.com/WPierce/archive/2007/11/26/Session-Keep-Alive-with-MonoRail-and-jQuery.aspx

-Bill

By: John Sonmez

John Sonmez — Mon, 07 Dec 2009 15:10:43 +0000

By: Paul Speranza

Paul Speranza — Mon, 07 Dec 2009 13:27:31 +0000

Simple but it works. If anyone has something different or better let’s hear it.

By: Reflective Perspective - Chris Alcock » The Morning Brew #492

John Sonmez — Tue, 08 Dec 2009 00:46:19 +0000

@Chris Brandsma Oops sorry, I wasn't clear enough. I meant the wrapped JQuery calls, but I suppose that is not a huge amount of overhead.

Comments on: Authenticated web services calls with Asp.Net MVC

Viky — Tue, 16 Feb 2010 04:20:53 +0000

Good one

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 15:54:45 +0000

@JC Grubbs: at worst it would result in 2 calls for every request. But for my application, I tend to see a lot of calls in bursts. That is why I do a time check on my call.

By: JC Grubbs

JC Grubbs — Tue, 08 Dec 2009 15:18:59 +0000

By: John Sonmez

John Sonmez — Tue, 08 Dec 2009 00:46:19 +0000

@Chris Brandsma Oops sorry, I wasn't clear enough. I meant the wrapped JQuery calls, but I suppose that is not a huge amount of overhead.

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 00:39:30 +0000

Hi guys,

Good suggestions all rounds. Pretty much proves I should have spent a little more time on the post. But I’ll look into what Sergio and Ben were talking about.

But a few things:
@John Sonmez: You shouldn’t have to write it for every page. Put the code in a js file and load it in a master page.

By: Sergio Pereira

Sergio Pereira — Mon, 07 Dec 2009 16:37:24 +0000

By: Bill Pierce

Bill Pierce — Mon, 07 Dec 2009 16:08:17 +0000

I would have opted for the simpler solution and just keep the user’s session alive as long as they do not navigate away from the site.

http://blechie.com/WPierce/archive/2007/11/26/Session-Keep-Alive-with-MonoRail-and-jQuery.aspx

-Bill

By: John Sonmez

John Sonmez — Mon, 07 Dec 2009 15:10:43 +0000

By: Paul Speranza

Paul Speranza — Mon, 07 Dec 2009 13:27:31 +0000

Simple but it works. If anyone has something different or better let’s hear it.

By: Reflective Perspective - Chris Alcock » The Morning Brew #492

Chris Brandsma — Tue, 08 Dec 2009 00:39:30 +0000

Hi guys,

Good suggestions all rounds. Pretty much proves I should have spent a little more time on the post. But I’ll look into what Sergio and Ben were talking about.

But a few things:
@John Sonmez: You shouldn’t have to write it for every page. Put the code in a js file and load it in a master page.

Comments on: Authenticated web services calls with Asp.Net MVC

Viky — Tue, 16 Feb 2010 04:20:53 +0000

Good one

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 15:54:45 +0000

@JC Grubbs: at worst it would result in 2 calls for every request. But for my application, I tend to see a lot of calls in bursts. That is why I do a time check on my call.

By: JC Grubbs

JC Grubbs — Tue, 08 Dec 2009 15:18:59 +0000

By: John Sonmez

John Sonmez — Tue, 08 Dec 2009 00:46:19 +0000

@Chris Brandsma Oops sorry, I wasn't clear enough. I meant the wrapped JQuery calls, but I suppose that is not a huge amount of overhead.

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 00:39:30 +0000

Hi guys,

Good suggestions all rounds. Pretty much proves I should have spent a little more time on the post. But I’ll look into what Sergio and Ben were talking about.

But a few things:
@John Sonmez: You shouldn’t have to write it for every page. Put the code in a js file and load it in a master page.

By: Sergio Pereira

Sergio Pereira — Mon, 07 Dec 2009 16:37:24 +0000

By: Bill Pierce

Bill Pierce — Mon, 07 Dec 2009 16:08:17 +0000

I would have opted for the simpler solution and just keep the user’s session alive as long as they do not navigate away from the site.

http://blechie.com/WPierce/archive/2007/11/26/Session-Keep-Alive-with-MonoRail-and-jQuery.aspx

-Bill

By: John Sonmez

John Sonmez — Mon, 07 Dec 2009 15:10:43 +0000

By: Paul Speranza

Paul Speranza — Mon, 07 Dec 2009 13:27:31 +0000

Simple but it works. If anyone has something different or better let’s hear it.

By: Reflective Perspective - Chris Alcock » The Morning Brew #492

Sergio Pereira — Mon, 07 Dec 2009 16:37:24 +0000

Comments on: Authenticated web services calls with Asp.Net MVC

Viky — Tue, 16 Feb 2010 04:20:53 +0000

Good one

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 15:54:45 +0000

@JC Grubbs: at worst it would result in 2 calls for every request. But for my application, I tend to see a lot of calls in bursts. That is why I do a time check on my call.

By: JC Grubbs

JC Grubbs — Tue, 08 Dec 2009 15:18:59 +0000

By: John Sonmez

John Sonmez — Tue, 08 Dec 2009 00:46:19 +0000

@Chris Brandsma Oops sorry, I wasn't clear enough. I meant the wrapped JQuery calls, but I suppose that is not a huge amount of overhead.

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 00:39:30 +0000

Hi guys,

Good suggestions all rounds. Pretty much proves I should have spent a little more time on the post. But I’ll look into what Sergio and Ben were talking about.

But a few things:
@John Sonmez: You shouldn’t have to write it for every page. Put the code in a js file and load it in a master page.

By: Sergio Pereira

Sergio Pereira — Mon, 07 Dec 2009 16:37:24 +0000

By: Bill Pierce

Bill Pierce — Mon, 07 Dec 2009 16:08:17 +0000

I would have opted for the simpler solution and just keep the user’s session alive as long as they do not navigate away from the site.

http://blechie.com/WPierce/archive/2007/11/26/Session-Keep-Alive-with-MonoRail-and-jQuery.aspx

-Bill

By: John Sonmez

John Sonmez — Mon, 07 Dec 2009 15:10:43 +0000

By: Paul Speranza

Paul Speranza — Mon, 07 Dec 2009 13:27:31 +0000

Simple but it works. If anyone has something different or better let’s hear it.

By: Reflective Perspective - Chris Alcock » The Morning Brew #492

Bill Pierce — Mon, 07 Dec 2009 16:08:17 +0000

I would have opted for the simpler solution and just keep the user’s session alive as long as they do not navigate away from the site.

http://blechie.com/WPierce/archive/2007/11/26/Session-Keep-Alive-with-MonoRail-and-jQuery.aspx

-Bill

Comments on: Authenticated web services calls with Asp.Net MVC

Viky — Tue, 16 Feb 2010 04:20:53 +0000

Good one

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 15:54:45 +0000

@JC Grubbs: at worst it would result in 2 calls for every request. But for my application, I tend to see a lot of calls in bursts. That is why I do a time check on my call.

By: JC Grubbs

JC Grubbs — Tue, 08 Dec 2009 15:18:59 +0000

By: John Sonmez

John Sonmez — Tue, 08 Dec 2009 00:46:19 +0000

@Chris Brandsma Oops sorry, I wasn't clear enough. I meant the wrapped JQuery calls, but I suppose that is not a huge amount of overhead.

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 00:39:30 +0000

Hi guys,

Good suggestions all rounds. Pretty much proves I should have spent a little more time on the post. But I’ll look into what Sergio and Ben were talking about.

But a few things:
@John Sonmez: You shouldn’t have to write it for every page. Put the code in a js file and load it in a master page.

By: Sergio Pereira

Sergio Pereira — Mon, 07 Dec 2009 16:37:24 +0000

By: Bill Pierce

Bill Pierce — Mon, 07 Dec 2009 16:08:17 +0000

I would have opted for the simpler solution and just keep the user’s session alive as long as they do not navigate away from the site.

http://blechie.com/WPierce/archive/2007/11/26/Session-Keep-Alive-with-MonoRail-and-jQuery.aspx

-Bill

By: John Sonmez

John Sonmez — Mon, 07 Dec 2009 15:10:43 +0000

By: Paul Speranza

Paul Speranza — Mon, 07 Dec 2009 13:27:31 +0000

Simple but it works. If anyone has something different or better let’s hear it.

By: Reflective Perspective - Chris Alcock » The Morning Brew #492

John Sonmez — Mon, 07 Dec 2009 15:10:43 +0000

Comments on: Authenticated web services calls with Asp.Net MVC

Viky — Tue, 16 Feb 2010 04:20:53 +0000

Good one

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 15:54:45 +0000

@JC Grubbs: at worst it would result in 2 calls for every request. But for my application, I tend to see a lot of calls in bursts. That is why I do a time check on my call.

By: JC Grubbs

JC Grubbs — Tue, 08 Dec 2009 15:18:59 +0000

By: John Sonmez

John Sonmez — Tue, 08 Dec 2009 00:46:19 +0000

@Chris Brandsma Oops sorry, I wasn't clear enough. I meant the wrapped JQuery calls, but I suppose that is not a huge amount of overhead.

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 00:39:30 +0000

Hi guys,

Good suggestions all rounds. Pretty much proves I should have spent a little more time on the post. But I’ll look into what Sergio and Ben were talking about.

But a few things:
@John Sonmez: You shouldn’t have to write it for every page. Put the code in a js file and load it in a master page.

By: Sergio Pereira

Sergio Pereira — Mon, 07 Dec 2009 16:37:24 +0000

By: Bill Pierce

Bill Pierce — Mon, 07 Dec 2009 16:08:17 +0000

I would have opted for the simpler solution and just keep the user’s session alive as long as they do not navigate away from the site.

http://blechie.com/WPierce/archive/2007/11/26/Session-Keep-Alive-with-MonoRail-and-jQuery.aspx

-Bill

By: John Sonmez

John Sonmez — Mon, 07 Dec 2009 15:10:43 +0000

By: Paul Speranza

Paul Speranza — Mon, 07 Dec 2009 13:27:31 +0000

Simple but it works. If anyone has something different or better let’s hear it.

By: Reflective Perspective - Chris Alcock » The Morning Brew #492

Paul Speranza — Mon, 07 Dec 2009 13:27:31 +0000

Simple but it works. If anyone has something different or better let’s hear it.

Comments on: Authenticated web services calls with Asp.Net MVC

Viky — Tue, 16 Feb 2010 04:20:53 +0000

Good one

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 15:54:45 +0000

@JC Grubbs: at worst it would result in 2 calls for every request. But for my application, I tend to see a lot of calls in bursts. That is why I do a time check on my call.

By: JC Grubbs

JC Grubbs — Tue, 08 Dec 2009 15:18:59 +0000

By: John Sonmez

John Sonmez — Tue, 08 Dec 2009 00:46:19 +0000

@Chris Brandsma Oops sorry, I wasn't clear enough. I meant the wrapped JQuery calls, but I suppose that is not a huge amount of overhead.

By: Chris Brandsma

Chris Brandsma — Tue, 08 Dec 2009 00:39:30 +0000

Hi guys,

Good suggestions all rounds. Pretty much proves I should have spent a little more time on the post. But I’ll look into what Sergio and Ben were talking about.

But a few things:
@John Sonmez: You shouldn’t have to write it for every page. Put the code in a js file and load it in a master page.

By: Sergio Pereira

Sergio Pereira — Mon, 07 Dec 2009 16:37:24 +0000

By: Bill Pierce

Bill Pierce — Mon, 07 Dec 2009 16:08:17 +0000

I would have opted for the simpler solution and just keep the user’s session alive as long as they do not navigate away from the site.

http://blechie.com/WPierce/archive/2007/11/26/Session-Keep-Alive-with-MonoRail-and-jQuery.aspx

-Bill

By: John Sonmez

John Sonmez — Mon, 07 Dec 2009 15:10:43 +0000

By: Paul Speranza

Paul Speranza — Mon, 07 Dec 2009 13:27:31 +0000

Simple but it works. If anyone has something different or better let’s hear it.

By: Reflective Perspective - Chris Alcock » The Morning Brew #492

Reflective Perspective - Chris Alcock » The Morning Brew #492 — Mon, 07 Dec 2009 08:35:21 +0000

[...] Authenticated web services calls with Asp.Net MVC – Chris Brandsma looks at how you can handle the problems caused by sessions timing out in complex Ajax based applications and how you can handle re-authentication [...]