Brahma Acharya

My feedback

  1. 278 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  1. BreezeJS Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    A quick update for this request:

    We’re probably 50% there today, but hope to get to 80% soon. This is certain to get done, but we’re just not there yet.

    Brahma Acharya commented  · 

    Am I missing something here? I believe the in-built attributes like [Required], [MinLength] etc. are available out of the box. If you use Entity Manager's saveChanges method, Breeze will throw the exception the way it would do on the server side.

  2. 385 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  21 comments  ·  1. BreezeJS Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Brahma Acharya commented  · 

    The way I would do this is just notify client that a particular change has occurred and let client refresh itself. Breeze then gives ample entry points.

    As a side note though the more challenging part comes when you have to use SignalR in a load balanced environment where you need to use a well thought out messaging architecture to notify changes..

  3. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  1. BreezeJS Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Brahma Acharya supported this idea  · 
  4. 214 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  1. BreezeJS Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Brahma Acharya commented  · 

    Patrick,
    Yes indeed there are ways to intercept the save change method. Without that Breeze would be dead, isn't it?
    You can override the SaveChangesCore method of EFContextProvider and do stuff that you wish in that method.

    We have a multi-tiered architecture and we have successfully used Breeze in conjunction with the Web API layer. The Web API layer has no reference to EF or access to any Data access components. Heck we even have web models (DTOs) which are completely separate from our entity models. We use Automapper for mapping between entities. No matter what the folks say, in an Enterprise level application, I would never ever expose my entire core entity model to anyone outside. Period. It just gives away way too much information (some of which might be your USP).

    I also believe Breeze should focus on the client side and make things easier (like creating Metadata, using proper REST convention for updates (rather than just one method) etc.). Having said that, Breeze makes so much easier for client side data management. It has reduced the client side complexity by orders of magnitude. And if you are planning for a SPA, not having something like Breeze doesn't make much sense.

    Cheers,

Feedback and Knowledge Base