[infinispan-issues] [JBoss JIRA] Resolved: (ISPN-354) Convert memcached.sh into startServer.sh

[Galder Zamarreno (JIRA)]

     [ https://jira.jboss.org/jira/browse/ISPN-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Galder Zamarreno resolved ISPN-354.
-----------------------------------

    Resolution: Duplicate Issue


See ISPN-353

> Convert memcached.sh into startServer.sh
> ----------------------------------------
>
>                 Key: ISPN-354
>                 URL: https://jira.jboss.org/jira/browse/ISPN-354
>             Project: Infinispan
>          Issue Type: Task
>          Components: Cache Server
>            Reporter: Galder Zamarreno
>            Assignee: Galder Zamarreno
>             Fix For: 4.1.0.ALPHA1
>
>
> > Galder
> >  
> > I notice you have a memcached.sh script to start the memcached server.   
> > I believe this should be something like startServer.sh, given that we  
> > are not actually starting memcached?  
>  
> Hmmm, depends how you look at it. You could say that we're starting  
> Infinispan implementation of memcached, which is memcached still 
>  
> >  
> > And perhaps the script could be reused for HotRod as well ... passing in  
> > a flag to specify which protocol to speak, perhaps something like:
> >  
> >    $ startServer.sh -p memcached
> >  
> > or
> >  
> >   $ startServer.sh -p hotrod
> >  
> > Perhaps org.infinispan.server.memcached.Main could be in the server/core  
> > module instead, and based on the protocol flag passed in, kick start the  
> > appropriate server?  WDYT?
>  
> I'm easy with either option. Having a single startServer.sh script fro  
> both servers makes it easy to maintain since there's a single script  
> rather than 2.
>  
> I'll create a JIRA for this.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira