<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Frans,<div>About using several ZOO-Kernel on the same server, i think Yoshida-san is using the current ZOO trunk and OpenStack, fto proceed to laod balancing and things like that.</div><div>I'm pretty sure he will be happy to share experiences with you about this.</div><div>Are you still on your Azure Cloud or moved somewhere else ?</div><div><br></div><div>Best,</div><div><br></div><div>Nick</div><div><br></div><div><br><div><div>Le 21 juin 2013 à 11:29, Frans Thamura a écrit :</div><br class="Apple-interchange-newline"><blockquote type="cite"><p dir="ltr">Waitng Yoshida reply the cloud implementation.of zoo that he know.</p><p dir="ltr">I am.interest to put a lot of zoo in paas cloudfoundry. To make hundreds zoo.instance in one server.</p><p dir="ltr">F</p>
<div class="gmail_quote">On Jun 21, 2013 4:27 PM, "Fenoy Gerald" <<a href="mailto:gerald.fenoy@geolabs.fr">gerald.fenoy@geolabs.fr</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
René,<br>
thanks a lot for the informations shared with ZOO-Project community it is really appreciated.<br>
<br>
As you said, we should probably start by upgrading to the current version of SpiderMonkey, moreover if it give ZOO-Kernel more performance in treating the JavaScirpt code, which we are happy to hear that it gets a future finally. Note that my proposal to move to V8 was following your comment about future of SpiderMonkey which sounded compromised to me. I know that thing changes and I am really happy that you keep us informed of this move. indeed, it is really important for us to keep current JavaScript code running as production applications may failed in other case.<br>
<br>
Frans,<br>
ZOO-Project is already running on cloud platform, I'm pretty sure that Yoshida can say more on this as he is the guy which is focussing on this specific topic.<br>
<br>
About tutorial on porting ZOO-Kernel to V8 I wonder if there is any honestly, I just gave the XPCOM component a try by making so many modifications in the code, that is one key reason why it was never committed on the SVN server.<br>
<br>
What about getting both support finally ? I mean, we may keep the SpiderMonkey support available as it is an ongoing project and we can add the V8 support. This way, when running configure you can specify the javascript engine you prefer to use. I also think that it may be important to not embed SpiderMonkey from a V8 version of the ZOO-Kernel, I don't know clearly here. But if this is the case then it makes even more sense to get both support.<br>
<br>
Waiting for your comments,<br>
Best regards<br>
<br>
Gérald Fenoy<br>
ZOO-Project PSC Chair<br>
<br>
Le 21 juin 2013 à 11:11, Frans Thamura <<a href="mailto:frans@meruvian.org">frans@meruvian.org</a>> a écrit :<br>
<br>
> Rene<br>
><br>
> I am not v8 person..yes. we have a work <a href="http://related.to/" target="_blank">related.to</a> it.<br>
><br>
> This thread i believe start my post to bring zoo to cloud. May be geralrd can answer this<br>
><br>
> F<br>
><br>
> On Jun 21, 2013 4:01 PM, "rldhont" <<a href="mailto:rldhont@gmail.com">rldhont@gmail.com</a>> wrote:<br>
> Hi Frans,<br>
><br>
> I'm a Mozilla contributor, and I just inform the Zoo Community that Mozilla restarted to propose an alternative to V8.<br>
><br>
> If it's really important for Zoo Community to get the current JavaScript services still working with less development it's possible.<br>
><br>
> I can't help to integrating V8.<br>
><br>
> René-Luc<br>
><br>
> Le 21/06/2013 10:52, Frans Thamura a écrit :<br>
>> Talking v8<br>
>><br>
>> Nodejs as v8 implementation raise up<br>
>><br>
>> I am interest with zoo repositioning.<br>
>><br>
>> If we can get small tutorial. We can help to <a href="http://put.in/" target="_blank">put.in</a> paas clous<br>
>><br>
>> On Jun 21, 2013 3:39 PM, "rldhont" <<a href="mailto:rldhont@gmail.com">rldhont@gmail.com</a>> wrote:<br>
>> Hi Zoo community,<br>
>><br>
>> After 2 years without publishing standalone spidermonkey, Mozilla has released stable source code based on Firefox 17.<br>
>> The next release will be SpiderMonkey24 based on Firefox 24.<br>
>><br>
>> You can find all the documentation here :<br>
>> <a href="https://developer.mozilla.org/en-US/docs/SpiderMonkey" target="_blank">https://developer.mozilla.org/en-US/docs/SpiderMonkey</a><br>
>><br>
>> The zoo can have parformant JavaScript without refactoring the provider.<br>
>><br>
>> René-Luc<br>
>><br>
>> Le 21/06/2013 10:30, Frans Thamura a écrit :<br>
>>> Awesome<br>
>>> That is cool<br>
>>> I love to be part.<br>
>>><br>
>>> Esp we can help to makr.zoo paas compatible<br>
>>> Nodejs can become reference<br>
>>><br>
>>> On Jun 21, 2013 3:27 PM, "Fenoy Gerald" <<a href="mailto:gerald.fenoy@geolabs.fr">gerald.fenoy@geolabs.fr</a>> wrote:<br>
>>> Frans,<br>
>>> I speak about replacing the JavaScript service support from Spider Monkey to V8 by now.<br>
>>><br>
>>> In the past, we got the ZOO-Kernel running as an XPCOM Component on windows platform (let say three years ago) but i would first like to try to make the ZOO-Kernel able to handle JavaScript services by using V8 rather than the current Spider Monkey.<br>
>>><br>
>>> In anyway, if some forces can join the effort and provide the V8 version of ZOO-Kernel it can be really useful.<br>
>>><br>
>>> Best regards,<br>
>>><br>
>>> Gérald Fenoy<br>
>>> ZOO-Project PSC chair<br>
>>><br>
>>><br>
>>><br>
>>> Le 21 juin 2013 à 10:22, Frans Thamura <<a href="mailto:frans@meruvian.org">frans@meruvian.org</a>> a écrit :<br>
>>><br>
>>> > Wow next zoo in v8<br>
>>> ><br>
>>> > That can easily become paas ready apps<br>
>>> ><br>
>>> > On Jun 21, 2013 3:12 PM, "Fenoy Gerald" <<a href="mailto:gerald.fenoy@geolabs.fr">gerald.fenoy@geolabs.fr</a>> wrote:<br>
>>> > Frans,<br>
>>> > I forward this email to the ZOO-Discuss mailing list.<br>
>>> ><br>
>>> > I would like to ask in anybody in the community want to handle the implementation of embedding the V8 engine in place of the SpiderMonkey in the ZOO-Kernel ?<br>
>>> ><br>
>>> > You can find some informations here : [1]<br>
>>> ><br>
>>> > Note that it is really important for us to get the current JavaScript services still working the same way after migrating to V8 engine as many production applications rely on it right now. Let say too much to re-implement everything.<br>
>>> ><br>
>>> > Waiting for your answer.<br>
>>> > Best regards,<br>
>>> ><br>
>>> > Gérald Fenoy<br>
>>> > ZOO-Project PSC Chair<br>
>>> ><br>
>>> > [1] <a href="http://zoo-project.org/trac/wiki/ZOO_SoC_Ideas#ZOO-Kernelrelatedideas" target="_blank">http://zoo-project.org/trac/wiki/ZOO_SoC_Ideas#ZOO-Kernelrelatedideas</a><br>
>>> ><br>
>>> > Le 15 juin 2013 à 04:54, Frans Thamura <<a href="mailto:frans@meruvian.org">frans@meruvian.org</a>> a écrit :<br>
>>> ><br>
>>> > > V8 is the chrome engine<br>
>>> > ><br>
>>> > > <a href="https://developers.google.com/v8/embed" target="_blank">https://developers.google.com/v8/embed</a><br>
>>> > ><br>
>>> > > because this tutorial, we can embed in paas, and nodejs also run on paas now<br>
>>> > ><br>
>>> > > nodejs is build on top of v8<br>
>>> > ><br>
>>> > ><br>
>>> > > --<br>
>>> > > Frans Thamura (曽志胜)<br>
>>> > > Shadow Master and Lead Investor<br>
>>> > > Meruvian.<br>
>>> > > Integrated Hypermedia Java Solution Provider.<br>
>>> > ><br>
>>> > > Mobile: <a href="tel:%2B628557888699" value="+628557888699">+628557888699</a><br>
>>> > > Blog: <a href="http://blogs.mervpolis.com/roller/flatburger" target="_blank">http://blogs.mervpolis.com/roller/flatburger</a> (id)<br>
>>> > ><br>
>>> > > FB: <a href="http://www.facebook.com/meruvian" target="_blank">http://www.facebook.com/meruvian</a><br>
>>> > > TW: <a href="http://www.twitter.com/meruvian" target="_blank">http://www.twitter.com/meruvian</a> / @meruvian<br>
>>> > > Website: <a href="http://www.meruvian.org/" target="_blank">http://www.meruvian.org</a><br>
>>> > ><br>
>>> > > "We grow because we share the same belief."<br>
>>> ><br>
>>> > _______________________________________________<br>
>>> > Zoo-discuss mailing list<br>
>>> > <a href="mailto:Zoo-discuss@lists.osgeo.org">Zoo-discuss@lists.osgeo.org</a><br>
>>> > <a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss</a><br>
>>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> Zoo-discuss mailing list<br>
>>><br>
>>> <a href="mailto:Zoo-discuss@lists.osgeo.org">Zoo-discuss@lists.osgeo.org</a><br>
>>> <a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss</a><br>
>><br>
><br>
> _______________________________________________<br>
> Zoo-discuss mailing list<br>
> <a href="mailto:Zoo-discuss@lists.osgeo.org">Zoo-discuss@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss</a><br>
<br>
</blockquote></div>
_______________________________________________<br>Zoo-discuss mailing list<br><a href="mailto:Zoo-discuss@lists.osgeo.org">Zoo-discuss@lists.osgeo.org</a><br>http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss<br></blockquote></div><br></div></body></html>