search

nsscreencast / comments

Public comments on NSScreencast.com
0 stars 0 forks source link

Windows Azure Mobile Services - NSScreencast #62

Open subdigital opened 3 years ago

subdigital commented 3 years ago

Written on 01/24/2015 11:00:49

URL: https://nsscreencast.com/episodes/59-windows-azure-mobile-services

subdigital commented 3 years ago

originally written by Brad on 04/01/2013 01:36:12

No comments? Really? No one else is disappointed that we're paying a subscription fee for this and our weekly episode is a Microsoft ad?

subdigital commented 3 years ago

originally written by Alek on 04/01/2013 12:18:37

Agreed! If this episode is sponsored, the subscribers should still get their weekly screencast which they're paying for.

subdigital commented 3 years ago

originally written by Anders Carlsson on 04/01/2013 14:59:21

Could not agree more. I don't like to pay for Microsoft adds!

subdigital commented 3 years ago

originally written by subdigital on 04/01/2013 16:08:52

This episode was in the planning before Microsoft approached me for sponsoring it. The episode is done in a similar style to previous episodes, just to present a good overview of what the service provides and how to build an app with it. The sponsorship was simply done to make the episode available to everyone, not just subscribers. I hear you concerns though, and making sure you find the screencasts valuable is very important to me. Thanks for commenting.

subdigital commented 3 years ago

originally written by Luke Hatcher on 04/02/2013 21:11:38

I think it's a fair criticism, but I also appreciate your response. Even during weeks when I'm not interested in the primary topic I tend to still pick up a few new ideas just from watching the way you approach things.

subdigital commented 3 years ago

originally written by Ray Beyer on 04/02/2013 21:15:25

I'm quite glad that this has one has been done! I'm always interested in server-side technologies, and was about to ask Ben, if this wouldn't be an interesting topic. I don't care, that MS is sponsoring this, and I also don't have the feeling that this is a bad move. I feel that I gotten quite some incredible advice from Bens work.

Just as an input: I also think Objective-Coud would be such a topic as well.

I'm not affilated with Ben or MS by the way ;-) Keep it up, Ben.

subdigital commented 3 years ago

originally written by John Clayton on 04/06/2013 14:42:58

Great episodes! I was curious on your thoughts about how Mobile Services compares to Parse and what sort of application would you consider using these sort of services as a back-end vs. rolling & hosting your own? The thought of not having to manage servers & not having to write cross-platform data access code is certainly appealing, but I worry about being locked-in with anything but a simple CRUD app.

The other issue I have with authentication & not being able to use anything other than the available providers. In the video you set the 'Twitter:###' from user.userId as the userid column, yet the table still has an ID column. You could instead authenticate with Twitter on the client & associate it with a non-social user rather than making it the authoritative user ID, but looking at the docs for the REST API I don't see a way to make use of Mobile Services authentication and security settings unless you use one of their authentication providers. With an associated provider I could send username + password, but would loose functionality (i.e. https://parse.com/docs/rest... )

Update: Yes - you can use your own authentication providers! http://www.thejoyofcode.com...

I guess these solutions trade convenience for control - you can get stuff working quickly, but if you want to do anything outside of what's provided you're in for a good deal of pain.

subdigital commented 3 years ago

originally written by subdigital on 04/08/2013 13:51:21

I am also pretty careful about the lock-in thing. I think it's definitely worth considering. We built a (very) simple app on Parse, and we chose it because it was so simple. For something advanced I generally lean towards owning the entire stack.
That said, it really is a balance on how much time you have to spend and where you want the most control. Having the most control over the entire stack means less time to work on features of your app.
As for the authentication piece, I think you can bring your own, you just have to be aware that you still can't trust the client, so whatever solution you come up with has to have the server do the verification as well. The docs don't cover everything, so make sure you check out the team's blogs as well. Josh Twist has a ton of useful information on Mobile Services over at http://thejoyofcode.com.