[Click] Two questions...

[Ian Rose]

They still work, but yes I see from trying them just now that they spit 
out a deprecation warning, so Socket is clearly preferable.  Thanks for 
the clarification.


Beyers Cronje wrote:
> Ian,
> 
> As far as I remember ToSocket and FromSocket were replaced by Socket 
> http://read.cs.ucla.edu/click/elements/socket
> 
> Beyers
> 
> On Wed, Jan 27, 2010 at 4:58 PM, Ian Rose <ianrose at eecs.harvard.edu 
> <mailto:ianrose at eecs.harvard.edu>> wrote:
> 
>     1) I don't think this is possible, although it would be nice!
> 
>     2) You could use ToSocket and FromSocket:
> 
>     http://read.cs.ucla.edu/click/elements/fromsocket
>     http://read.cs.ucla.edu/click/elements/tosocket
> 
>     So one possible implementation would be, myrouter1.click:
> 
>     (other elements) -> ToSocket(UNIX, my_click_socket);
> 
>     and myrouter2.click:
> 
>     FromSocket(UNIX, my_click_socket) -> (other elements)
> 
>     This is using a UNIX domain socket but you could also use TCP or UDP if
>     you prefer.
> 
>     cheers,
>     -Ian
> 
> 
>     remi.clavier at orange-ftgroup.com
>     <mailto:remi.clavier at orange-ftgroup.com> wrote:
>      >
>      > 1) it's possible or not to use something like a include directive
>     into my router.click file? The includded file would content
>     elementClass or compound definitions?
>      >
>      > 2) for test, i need to instatiate two differents configuration
>     (to launch  ./click myrouter1.click and .click myrouter2.click in
>     two different consol and allow to my two differens router to
>     comunique together ( output of router connceted to outpout of router2.
>      > I's possible?
>      > Wich element may be used at this "intercommuniction port ?
>      > I precise : I work at user-level end my frames are not ethernet
>     nor ip compliant
>      >
>      >
>      > Thanks
>      >
>      >
>      > Rémi
>      >
>      > *********************************
>      > This message and any attachments (the "message") are confidential
>     and intended solely for the addressees.
>      > Any unauthorised use or dissemination is prohibited.
>      > Messages are susceptible to alteration.
>      > France Telecom Group shall not be liable for the message if
>     altered, changed or falsified.
>      > If you are not the intended addressee of this message, please
>     cancel it immediately and inform the sender.
>      > ********************************
>      >
>      >
>      > _______________________________________________
>      > click mailing list
>      > click at amsterdam.lcs.mit.edu <mailto:click at amsterdam.lcs.mit.edu>
>      > https://amsterdam.lcs.mit.edu/mailman/listinfo/click
> 
>     _______________________________________________
>     click mailing list
>     click at amsterdam.lcs.mit.edu <mailto:click at amsterdam.lcs.mit.edu>
>     https://amsterdam.lcs.mit.edu/mailman/listinfo/click
> 
>