state

i needed help refactoring the following class, Following is a class Operation with variety of Operations in switch : i want to avoid the switch statement.I read few articles on using polymorphism and state pattern .but when i refactor the classes i dont get access to many variables,properties Im confused on whether to use operation as abstract class or to implement an interface. Just wanted to know which type of refactoring will help in this case polymorphism or state pattern? And when to use them? public class Operation { public enum OperationType { add, update, delete, retrieve } public enum

In the state pattern how is this modeled ? state A to state B on trigger X and conditon C1 when current state is A state A to state C on trigger X and condition C2 when current state is A how is this usually accomplished ? I have a lot of guard conditions that I may need to implement. That's pretty standard see e.g. this example . [Edited on basis it's not homework!] Assuming I understand right: You have one event ( X ) which can trigger one of two possible transitions Selecting which transition to fire is made according to which condition holds true ( C1 or C2 ) If so that's a standard case

I'm looking for a solution to a design problem. This will take a bit of explaining. I would post code, but that woul make this even longer. I have a custom generic collection I use to hold Business Objects as needed. For easy of reference, call the business objects BO and the generic collection GC . Inside GC I have a private collection of those business objects that have been flagged for deletion. Call this private collection PDC . I can have an arbitrary number of GC's, each with their own PDC, at any one time, plus other BOs that aren't in any collection. When I save changes I loop over all

Apache Beam has recently introduced state cells, through StateSpec and the @StateId annotation, with partial support in Apache Flink and Google Cloud Dataflow. My question is about state garbage collection, in the case where a stateful DoFn is used on a windowed stream. Typically, state is removed (garbage collected) by the runner when the window expires (i.e. the watermark passes the end of the window). However, consider the case where window panes are triggered early, and the fired panes are discarded: input.apply(Window.<MyElement>into(CalendarWindows.days(1)) .triggering(AfterWatermark

I am new to angular Js. My application flow is as below: 1) I have a view controller wherein, each view controller sets the breadcrumb data with the help of Breadcrumbs factory. 2) Breadcrumbs factory takes data from view controller and attaches data to $location.$$state object.(reason for storing in state object is if back button is pressed, view controller doesn't instantiate so I can refer history data for breadcrumbs ) below is code to attach data to state object: var state = $location.state(); state.breadcrumb = breadcrumbData; $location.replace().state(state); 3) I have also created