On Sun, Feb 20, 2011 at 8:18 AM, Amila Suriarachchi <[email protected]> wrote:

> In General is it a best practice to use main sequence for some specific
> task?
>
> I think we should always use Proxy service for those things and main
> sequence can be used as a default path
> for any undispatched message for a proxy service.
>

+1. This was my view too...

>
> And also I would like to see a proxy service is always as a web service.
> Then it should have a wsdl and client code should
> written by generating the code with that.
>
> thanks,
> Amila.
>
> On Sat, Feb 19, 2011 at 8:24 PM, Samisa Abeysinghe <[email protected]>wrote:
>
>> For e.g. see:
>> http://wso2.org/project/esb/java/3.0.1/docs/samples/qos_mediation_samples.html#Sample100
>>
>> <http://wso2.org/project/esb/java/3.0.1/docs/samples/qos_mediation_samples.html#Sample100>It
>> takes about 10 minutes to read and understand the scenario and you still
>> remain doubtful if you got the thing right. For e.g. is this sample showing
>> security between client and ESB or ESB & back-end?
>>
>> Why not add a diagram each on the scenario being addressed??
>>
>> Also, as discussed in the road-map discussion, all these samples also need
>> instructions on how to get them done with the UI. Which means, we cannot use
>> the same doc as from the Synapse docs. Need to have some screenshots on how
>> to pick the sec. policy etc.
>>
>> Also, I am not clear if it is a proxy service or the main sequence that we
>> are securing with this sample.
>>
>> Thanks,
>> Samisa...
>>
>> Samisa Abeysinghe
>> VP Engineering
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>>
>>
>>
>> _______________________________________________
>> Carbon-dev mailing list
>> [email protected]
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
> Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to