You can also keep things skinny by leveraging components here maybe.
Am Samstag, 18. Juli 2015 13:21:20 UTC+2 schrieb Jeremy Burns:
>
> Yup - I understand that. But a method in a skinny controller (which I
> appreciate is the element that should provide feedback on progress) hands
> off to a sin
Yup - I understand that. But a method in a skinny controller (which I
appreciate is the element that should provide feedback on progress) hands off
to a single model function which then follows business rules and runs a series
of processes in sequence. So my question is “when the progress one wa
multi-step sounds like the C in MVC. the model itself has nothing to do
with stateful requests IMO.
Am Freitag, 17. Juli 2015 11:08:21 UTC+2 schrieb Jeremy Burns:
>
> What about the situation where you have a multi-step process inside a
> model/s and you want to make the progress status availabl
Mark,
Thanks a lot, solved my problem.
On Fri, Jul 17, 2015 at 5:55 AM, euromark wrote:
> Your models should stay stateless, as such you should never internally use
> the session.
> Instead, pass the data to the model layer or use events to pass them
>
> Use https://github.com/UseMuffin/Footpri
What about the situation where you have a multi-step process inside a model/s
and you want to make the progress status available to javascript calls?
> On 17 Jul 2015, at 09:55, euromark wrote:
>
> Your models should stay stateless, as such you should never internally use
> the session.
> Inst
Your models should stay stateless, as such you should never internally use
the session.
Instead, pass the data to the model layer or use events to pass them
Use https://github.com/UseMuffin/Footprint
Mark
Am Donnerstag, 16. Juli 2015 23:03:45 UTC+2 schrieb Rafael Queiroz:
>
> Hi guys,
>
> I ne
