Remove batching
Reported by bahuvrihi | February 10th, 2009 @ 09:05 PM | in Tap-1.0.0
As hard as it is to dump the work that went into batching, it really should be removed. Batching adds unnecessary complexity to tap for a feature that is not likely to be used frequently. Batch behavior can be implemented independently, for instance through workflows.
The main advantage of batching is multiplicity from configuration. Compelling as that is, it adds major headaches when it comes to joins like SyncMerge. In the long run, it's more important to make the framework clear.
Comments and changes to this ticket
-
bahuvrihi February 11th, 2009 @ 12:05 PM
- Assigned user set to “bahuvrihi”
- State changed from “new” to “resolved”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
A framework for making configurable, file-based tasks and workflows.
bahuvrihi