Thanks Stephen On Tuesday, April 5, 2016 at 3:42:25 PM UTC+5:30, Stephen Connolly wrote: > > SSH is encrypted, but uses Blocking I/O (unless you use the CloudBees > proprietary NIO SSH Slave connector) so scalability can be limited. > > JNLPAgentProtocol2 is unencrypted and uses Non-Blocking I/O, so you get > back-pressure when the server is under load, but good scalability. > > JNLPAgentProtocol3 is lightweight encrypted but uses Blocking I/O, so > scalability may be limited again, but I have yet to test as I need to > recalibrate my test rig. > > I am currently working on JNLPAgentProtocol4 which will be Non-Blocking > I/O and full TLS encryption. > > On 5 April 2016 at 09:37, JenkinsJunkyard <[email protected] > <javascript:>> wrote: > >> Thanks for the reply jpd4nt. >> for anybody - any other advantages between these two protocols. >> >> Thank, >> Naveen >> >> On Monday, April 4, 2016 at 10:43:18 PM UTC+5:30, jpd4nt wrote: >>> >>> Hi Naveen. >>> >>> I find ssh option more robust because our Jenkins master is behind a >>> load balancer so the web start has to go through that, we use AWS ELB and >>> sometimes the connection breaks. >>> >>> Also with a fix master its easier to set the access rules that for a >>> slave ringing home back to the master. >>> >>> On Monday, 4 April 2016 15:30:10 UTC+1, JenkinsJunkyard wrote: >>>> >>>> Hello, >>>> >>>> I am configuring jenkins from linux to windows, with windows as slave. >>>> I have configured in both protocols. >>>> I see java web start very easy to configure the master slave. But while >>>> configuring the windows slave through SSH it is more complicated compared >>>> to java web start. >>>> >>>> I wanted to understand, what are the advantages with respect to >>>> technical perspective, simplicity and security with the configuration of >>>> windows slave and linux as master. >>>> >>>> Please let me know your suggestions. >>>> >>>> Thanks, >>>> Naveen >>>> >>> 68 >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/66c95ce2-3d12-4f95-85e2-d9683bc086c3%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/66c95ce2-3d12-4f95-85e2-d9683bc086c3%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > >
-- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b22fa89e-1ae0-4ea1-b518-8e9f47cf307b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
