Comments on: Building Single Page Apps with HTML5, Knockout, jQuery, and Web API – Part 3 – Server Technologies

By: John

John — Wed, 16 Jan 2013 13:05:16 +0000

Mark – Certainly. You can create the back end as you wish as long as you expose it to a web service of some sort. Preferably one that reveals JSON over http, for ease of Ajax calls.

By: Mark

Mark — Tue, 15 Jan 2013 16:08:52 +0000

We’d like to leverage the Web API, but no need for EF as we already have business objects / domain objects (not to mention rich set of method arguments) developed that could just be called from the service methods.
Is this workable with the concept of context object?

By: David

David — Thu, 10 Jan 2013 04:14:21 +0000

Correction:
return new EFRepository(DbContext);

By: David

David — Thu, 10 Jan 2013 04:09:53 +0000

Thanks for the bump James. I was starting to think it must have been a stupid question. I would be very interested to know the benefits of the current implementation over this simplification:
* Delete the RepositoryFactories class.
* Change IRepositoryProvider to this:
DbContext DbContext { get; set; }
IRepository Rooms();
IRepository TimeSlots();
IRepository Tracks();
ISessionsRepository Sessions();
IPersonsRepository Persons();
IAttendanceRepository Attendance();

* Then implement each of these in RepositoryProvider; e.g.:
public IRepository Rooms()
{
return new EFRepository(DbContext);
}
* Then simply call these from the UOW, e.g.:
public IRepository Rooms { get { return RepositoryProvider.Rooms(); } }

Cheers.

By: James Barrow

James Barrow — Tue, 08 Jan 2013 23:55:36 +0000

Hi John,

I’m posting because I’m also interested in the question David had regarding the Unit of Work pattern you use, and how to go about doing unit testing with this approach.

Also, typically I’ve seen that there would be another service layer, between the web and data layers, with dependencies: web > service > data

That way, the web controller just calls a service, and in the service you actually use the unit of work that interacts with the database, so in my experience I’ve seen that you typically wouldn’t test the controller, but rather the service, and stub/mock out anything it’s using. In this case, that would mean mocking out the unit of work.

So please if possible, can you get back to David’s question, as I think it would be a common question

Cheers,

James

By: LOB Gamification Service Admin Website: Data Services « Dan's Green Shoes

LOB Gamification Service Admin Website: Data Services « Dan's Green Shoes — Fri, 14 Dec 2012 18:32:48 +0000

[...] John Papa’s course “Single Page Apps with HTML5, Web API, Knockout and jQuery”. From John’s blog, the SPA has lots of patterns “including the Repository Pattern (to expose the data in a [...]

By: John

John — Fri, 14 Dec 2012 13:51:27 +0000

ifrit – I’ll be blogging about this in the next few days

By: ifrit

ifrit — Fri, 14 Dec 2012 05:28:31 +0000

Very nice post, thank you very much.
Just wondering how I’de manage the LoginModel in such architecture

By: Abhi

Abhi — Fri, 07 Dec 2012 15:34:50 +0000

Thanks John for the prompt response. That makes perfect sense.

I have started the Pluralsight course and am looking forward to do my first SPA app.

Thanks,
Abhi.

By: John

John — Fri, 07 Dec 2012 14:34:25 +0000

Hi Abhi,

Sure. What you use on the back end is not important for a SPA. You can use DB2 and expose your data any way you like via a web service to the client. The “SPA” is all on the client.