[sakai2-tcc] Infrastructure discussion for future meeting?

John Bush john.bush at rsmart.com
Wed Mar 13 13:12:05 PDT 2013


I think David is asking why is that the requirement ?  We shouldn't be
letting our demo dictate our platform.  Maybe that not the compelling
reason, but then if not one only one process?  What makes that a
non-starter ?  I understand this has been our position in the past but
what is the reason we need to work towards that necessarily into the
future.  What if only certain things didn't work in a one jvm/tomcat
demo world, that be consistent with how things are now.   I mean
things like ldap don't work ootb right now without an ldap server
living somewhere.

On Wed, Mar 13, 2013 at 12:57 PM, Aaron Zeckoski <azeckoski at unicon.net> wrote:
> I mean it should run in one JVM and tomcat. I don't think I can add
> much to that.
> -AZ
>
>
> On Wed, Mar 13, 2013 at 3:47 PM, David Adams <da1 at vt.edu> wrote:
>>
>> Aaron Zeckoski wrote:
>>> Mostly I mean running in the same tomcat (think the Sakai demo).
>>> If it won't work as part of the Sakai binary/demo then that's a
>>> non-starter IMO.
>>
>> Could you explain more what the issues with this would be? Is there a
>> reason why the demo/binary couldn't start up and manage two processes
>> just as well as it does one?
>>
>> -dave
>> _______________________________________________
>> sakai2-tcc mailing list
>> sakai2-tcc at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>
>
>
> --
> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc



--
John Bush
602-490-0470


More information about the sakai2-tcc mailing list