cleaned data - Page 103

New Data Web Controls Enhancements in ASP.NET 4.0 Give ASP.NET Developers More Control

This ASP.NET tutorial explores a number of enhancements made to the data Web controls in ASP.NET 4.0.

White Hats Take Charge of Data Security

As cybercrime continues to grow, the 'good guys' are fighting back as they maintain data security ensure that crime doesn't pay.

Application Developers Worry as Data Plans Are Capped

Will smartphone users stop downloading so many apps as the all-you-can-eat data buffet ends?

Application Developers Worry as Data Plans Are Capped

Will smartphone users stop downloading so many apps as the all-you-can-eat data buffet ends?

I have create some kind of data pipeline to transform coordinate data into more useful information. Here is the shell of pipeline: public class PositionPipeline { protected List<IPipelineComponent> components; public PositionPipeline() { components = new List<IPipelineComponent>(); } public PositionPipelineEntity Process(Position position) { foreach (var component in components) { position = component.Execute(position); } return position; } public PositionPipeline RegisterComponent(IPipelineComponent component) { components.Add(component); return this; } } Every IPipelineComponent accepts and returns the same type - a PositionPipelineEntity. Code: public interface IPipelineComponent { PositionPipelineEntity Execute(PositionPipelineEntity position); } The PositionPipelineEntity needs to have many properties, many which are unused in certain components and required in others. Some properties will also have become redundant at the end of the pipeline. For example, these components could be executed: TransformCoordinatesComponent: Parse the raw coordinate data into a Coordinate type. DetermineCountryComponent: Determine and stores country code. DetermineOnRoadComponent: Determine and store whether coordinate is on a road. Code: pipeline .RegisterComponent(new TransformCoordinatesComponent()) .RegisterComponent(new DetermineCountryComponent()) .RegisterComponent(new DetermineOnRoadComponent()); pipeline.Process(positionPipelineEntity); The PositionPipelineEntity type: public class PositionPipelineEntity { // Only relevant to the TransformCoordinatesComponent public decimal RawCoordinateLatitude { get; set; } // Only relevant to the TransformCoordinatesComponent public decimal RawCoordinateLongitude { get; set; } // Required by all components after TransformCoordinatesComponent public Coordinate CoordinateLatitude { get; set; } // Required by all components after TransformCoordinatesComponent public Coordinate CoordinateLongitude { get; set; } // Set in DetermineCountryComponent, not required anywhere. // Requires CoordinateLatitude and CoordinateLongitude (TransformCoordinatesComponent) public string CountryCode { get; set; } // Set in DetermineOnRoadComponent, not required anywhere. // Requires CoordinateLatitude and CoordinateLongitude (TransformCoordinatesComponent) public bool OnRoad { get; set; } } Problems: I'm very concerned about the dependency that a component has on properties. The way to solve this would be to create specific types for each component. The problem then is that I cannot chain them together like this. The other problem is the order of components in the pipeline matters. There is some dependency. The current structure does not provide any static or runtime checking for such a thing. Any feedback would be appreciated.

Search Results

Search found 58779 results on 2352 pages for 'cleaned data'.

Page 103/2352 | < Previous Page | 99 100 101 102 103 104 105 106 107 108 109 110 | Next Page >

- by davenewza

- by Douglas

- by Nilesh

- by dmt0

- by VeeKay

- by tjb1982

- by Jeffrey Kevin Pry

- by Amir Eldor

- by user702295

- by iamcreasy

- by Anon

- by user1493730

- by Btibert3

- by Mike C

< Previous Page | 99 100 101 102 103 104 105 106 107 108 109 110 | Next Page >