[Opa] Network to transit information of more than one type

Rudy Sicard rudy.sicard at mlstate.com
Tue Apr 17 12:42:53 UTC 2012


Hi,

Not sure I understand your problem.

type trade_or_order = trade or order

may be a good starting point

On 17/04/2012 13:30, amulya rattan wrote:
> What if I want to transfer these two types of messages in my network:
>
> 1. type trade = {int ref_no, int account,int buy_sell, string 
> instrument, string attributes}
> 2. type order = {int quantity, String security, int amount}
>
> I can't extend one type of message from another there. Hope this makes 
> my point clear.
>
> ~Amulya
>
> On Tue, Apr 17, 2012 at 7:15 AM, Frederic Ye <frederic.ye at mlstate.com 
> <mailto:frederic.ye at mlstate.com>> wrote:
>
>     You can easily extend the message type :
>
>     type stopNetwork = { string error, string code }
>
>     type message = {string author, string text} or stopNetwork
>
>     On Apr 17, 2012, at 1:12 PM, amulya rattan wrote:
>
>     > All,
>     >
>     > Below statement creates a cloud network of the type of a network
>     that transits information of type message. Is there a way to
>     create a network that can transit different types of messages? For
>     e.g. I want to have an additional type that I want to transmit
>     through the network: type stopNetwork = { string error, string
>     code }. Any suggestions?
>     >
>     >
>     > room = Network.network(message) (Network.cloud("room"))
>     > _______________________________________________
>     > Opa mailing list
>     > Opa at lists.owasp.org <mailto:Opa at lists.owasp.org>
>     > https://lists.owasp.org/mailman/listinfo/opa
>
>     Frederic Ye.
>
>
>
>
> _______________________________________________
> Opa mailing list
> Opa at lists.owasp.org
> https://lists.owasp.org/mailman/listinfo/opa

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/opa/attachments/20120417/dbd8b5f8/attachment.html>


More information about the Opa mailing list