Anyone who has had to write software to send high volumes of emails, upload and an unknown number of files to a server, perform distributed calculations, update stock tickers or even create some load balancing service would know the difficulty in making it fast and reliable or simply just getting it to work. They would appreciate the difficulty in using cryptic components that are hard to understand and provide complex interfaces when all you want is to focus on getting the job done instead of tussling with their complexities. Pipeline.NET is a high-performance .NET component that fills this gap by providing a reliable and easy to use API.
Frequently asked questions
Exactly what does it do?
Pipeline.NET allows the scheduling of an unlimited number of tasks while limiting the number of tasks that are running at any one time.
What is the benefit of this?
Having an easy way to fire and forget your tasks is definitely a huge plus but executing an unlimited number of tasks simultaneously may be counter-productive to performance. Running tasks that are not time sensitive this may not be a problem but, if you wish real-time performance then it is best to limit the number of tasks running to the numbers of processor cores available.
Is it easy to configure?
To get started using the PipelineScheduler simply create a new instance using all the default parameters which are automatically customised for the device that’s running the software.
new PipelineScheduler();. See all the configuration parameters.
Can I change the scheduling algorithm?
Pipeline.NET is built with a pluggable scheduling algorithm architecture allowing custom algorithms to be used very easily. Pipeline.NET comes with both First Come First Serve (FCFS) and Priority scheduling with FCFS used as the default.
How does it work?
What .NET applications will it work with?
Pipeline.NET can be used in all variants of .NET applications as long as they are using the .NET Framework 3.5 or above including web applications and XML & WCF services, windows services, WPF & WinForm applications, etc.
Does it work in the background?
Pipeline.NET runs all tasks on background threads but provides the configuration option to choose either ThreadPool or non-ThreadPool threads.
Is their any API documentation?
Yes. The API documentation can be found here.
Are there “get started” examples?
All the API documentation provide examples on how to use the component.
What do you get when you buy Pipeline.NET?
- .NET 3.5 Assemblies
- Debug files (PDB)
- XML comments (Intellisense)
- Get Started documentation
- Documented API
- Demo applications
- C# Source Code
Example applications where you can use Pipeline.NET?
- Uploading files via FTP, REST or another API
- Distributed calculations
- Sending an unknown quantity of emails
- Handling UI driven workload
- Load balancing service
- Updating stock tickers
- Plus many more usages
This component is built using the .NET 3.5 Framework which means it can be used in all .NET applications that are using the 3.5 framework or newer.
You can immediately use this within your application and is very simple. Ask any questions or suggest features at support.avantprime.com.