[OSC_dev] Application Profiles

[salsaman at xs4all.nl]

On Sun, December 21, 2008 13:59, Nicholas J Humfrey wrote:
>> Then you just send /reply_to <port> where port is also the sending
>> port.
>>
>> Or we could say that <port> is optional, and if ommitted, replies
>> are sent
>> to originating port/host.
>
> So when sending the '/reply_to' message you are creating a redirect
> table on the sever saying when you receive a message from host1:port1,
> please reply to host2:port2?
>


In my app I assume that there is only one controlling application, so
simply all replies are sent to host:port.



>
>> Why remove the flexibility that someone might want to do otherwise ?
>
> I guess I just don't see the need for it. Seems like an edge case.
>
>
>> And why are you not commenting on the wiki ? I am assuming if nobody
>> comments there then there is a general agreement.
>
> I have left several comments on the wiki. Although I find it pretty
> hard to follow. Should I disregard the homepage and only look at the
> Summary Page?
>

Yes, I am trying to keep the summary page updated now.

I have discovered a nasty problem with the proposed get/set protocol which
needs to be resolved somehow.

Gabriel.




>
> nick.
>
> _______________________________________________
> OSC_dev mailing list
> OSC_dev at create.ucsb.edu
> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev
>