#emberjs

Hello!

someone expert in ember-data will helpme with this question? http://discuss.emberjs.com/t/relationship-id-re...

please, and thanks

!get nombom

alias nombom='npm cache clear && bower cache clean && rm -rf node_modules bower_components && npm install && bower install'

Okay I like ember a lot, but is this situation even logical?? Imagine an ember app working with rails which serves as a backend. is it possible to have seperate types of sessions within the ember app, for instance, users/admins?

or customers/vendors?

slothman: ?

locks: What I'm really asking, is a SPA capable of serving different types of user sessions?

why wouldn't it

what's the difference to a non-SPA

locks: can you think of any examples of SPA's that do this?

any SPA with an admin backoffice

locks:

how you architect it is up to your team to decide

it's kind of like monoliths and SOA

https://www.npmjs.com/package/ember-can there's this for example

for authorization in your application

Is it true that defaultValues with relationships is not working

in Ember data

Hey, I have a question I'm not really sure how to articulate. I know saving my models will sometimes fail for various reasons (mostly dodgy internet connection). What I want is to be able to just keep on working, have ember retry in the background, and then maybe fail after a few tries. I know how to do that (by overriding the save method), but I wonder, is there a more robust ember solution that includes

for example a cache layer, so first models are saved to local storage, and then flushed to server every few seconds or whatever? Or not?

you don't need to override the save method

I don't think there's anything robust like that

closest I know is ember-sync

locks, thanks, looking into that.

locks, I know I don't need to override the save method, I could just use a custom function, but overriding that feels cleaner, no?

I don't see how

you have the failure handler

locks, ember-sync looks exactly like what I was looking for.

nice :D

thanks. :P

I think there's even an example of retrying in the guides

locks, there is

but I find having to do

retry(model.save())

or whatever all over the place

much uglier than

model.save()

without having to change existing code

I don't like implicitness :P

it's a per-model override

it is implicit, but it's also the intended behaviour

all around