> I've been writing some simple code using FlexiMerge/FlexiRoute, and I'm
>> wondering why both have a single required "OperationAttributes" parameter?
>> Maybe there should be a * at the end to allow 0-* such parameters?
>>
>
> You can combine attributes with the "and" combinator if you want to attach
> more than one.
>
Can I attach 0? :)
> A side-question, I'm not really sure why this is so, but when I have a
>> Merge, I can just do:
>>
>> in ~> merge ~> out
>>
>> But when I have a FlexiMerge, I need to do:
>>
>> in ~> flexiMerge.in0
>> flexiMerge.out ~> out
>>
>> it seems Merge's shape is also an Inlet, but I can't find that in the
>> code :)
>>
>
> No, Merge has a shape of UniformFanIn. The sugared version of connecting
> merge/broadcast only works because the DSL understands UniformFanin/Fanout
> shapes, but it does not know about other shapes, since they can have
> different types for each port (inlet/outlet).
>
Ah! Now I have:
class SplitRoute[T](splitFn: T => Either[T, T]) extends FlexiRoute[T,
UniformFanOutShape[T, T]](
new UniformFanOutShape(2), OperationAttributes.name("SplitRoute")) { ... }
and I can use the nicer DSL.
Thanks,
Adam
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ:
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
