5 ms·
SWF is a developer tar baby. Don't touch. It's incredibly complex for what little it does. At the service side, a simple queue server would replace it. Ever
by codeonfire 11y ago
SWF is a developer tar baby. Don't touch. It's incredibly complex for what little it does. At the service side, a simple queue server would replace it. Everything about the 'workflow' is implemented on the client using whatever latest java abomination like AOP backed annotations.
- AReallyGoodName 11y agoAuthor here. I thought that too at first. It's actually straightforward though. I now have a video transcoding workflow that works well. It's not SWF that's the problem. It's actually really straightforward to use. AOP is not required, annotations are not required and those design patterns are not required. It's just the really messed up documentation that makes you think this. Check the bottom of the above article. You just take the C# sample and copy and paste it onto Java. Change the syntax to Java. It gets a bit more verbose but is still trivial to grok.
- optimusclimb 11y agoDid you contact support or email someone responsible for SWF in some way, or just write the blog post?
- AReallyGoodName 11y agojcrites from Amazon has responded above in this thread which is nice.