[Zoo-discuss] Embed V8

Fri Jun 21 02:51:19 PDT 2013

We use both here in azure and openstack. Run well.still here

My need is to run on cloudfoundry or openshift
On Jun 21, 2013 4:37 PM, "Nicolas Bozon" <nicolas.bozon at cartoworks.com>
wrote:

> Frans,
> 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.
> I'm pretty sure he will be happy to share experiences with you about this.
> Are you still on your Azure Cloud or moved somewhere else ?
>
> Best,
>
> Nick
>
>
> Le 21 juin 2013 à 11:29, Frans Thamura a écrit :
>
> Waitng Yoshida reply the cloud implementation.of zoo that he know.
>
> I am.interest to put a lot of zoo in paas cloudfoundry. To make hundreds
> zoo.instance in one server.
>
> F
> On Jun 21, 2013 4:27 PM, "Fenoy Gerald" <gerald.fenoy at geolabs.fr> wrote:
>
>> René,
>> thanks a lot for the informations shared with ZOO-Project community it is
>> really appreciated.
>>
>> 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.
>>
>> Frans,
>> 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.
>>
>> 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.
>>
>> 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.
>>
>> Waiting for your comments,
>> Best regards
>>
>> Gérald Fenoy
>> ZOO-Project PSC Chair
>>
>> Le 21 juin 2013 à 11:11, Frans Thamura <frans at meruvian.org> a écrit :
>>
>> > Rene
>> >
>> > I am not v8 person..yes. we have a work related.to it.
>> >
>> > This thread i believe start my post to bring zoo to cloud. May be
>> geralrd can answer this
>> >
>> > F
>> >
>> > On Jun 21, 2013 4:01 PM, "rldhont" <rldhont at gmail.com> wrote:
>> > Hi Frans,
>> >
>> > I'm a Mozilla contributor, and I just inform the Zoo Community that
>> Mozilla restarted to propose an alternative to V8.
>> >
>> > If it's really important for Zoo Community to get the current
>> JavaScript services still working with less development it's possible.
>> >
>> > I can't help to integrating V8.
>> >
>> > René-Luc
>> >
>> > Le 21/06/2013 10:52, Frans Thamura a écrit :
>> >> Talking v8
>> >>
>> >> Nodejs as v8 implementation raise up
>> >>
>> >> I am interest with zoo repositioning.
>> >>
>> >> If we can get small tutorial. We can help to put.in paas clous
>> >>
>> >> On Jun 21, 2013 3:39 PM, "rldhont" <rldhont at gmail.com> wrote:
>> >> Hi Zoo community,
>> >>
>> >> After 2 years without publishing standalone spidermonkey, Mozilla has
>> released stable source code based on Firefox 17.
>> >> The next release will be SpiderMonkey24 based on Firefox 24.
>> >>
>> >> You can find all the documentation here :
>> >> https://developer.mozilla.org/en-US/docs/SpiderMonkey
>> >>
>> >> The zoo can have parformant JavaScript without refactoring the
>> provider.
>> >>
>> >> René-Luc
>> >>
>> >> Le 21/06/2013 10:30, Frans Thamura a écrit :
>> >>> Awesome
>> >>> That is cool
>> >>> I love to be part.
>> >>>
>> >>> Esp we can help to makr.zoo paas compatible
>> >>> Nodejs can become reference
>> >>>
>> >>> On Jun 21, 2013 3:27 PM, "Fenoy Gerald" <gerald.fenoy at geolabs.fr>
>> wrote:
>> >>> Frans,
>> >>> I speak about replacing the JavaScript service support from Spider
>> Monkey to V8 by now.
>> >>>
>> >>> 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.
>> >>>
>> >>> In anyway, if some forces can join the effort and provide the V8
>> version of ZOO-Kernel it can be really useful.
>> >>>
>> >>> Best regards,
>> >>>
>> >>> Gérald Fenoy
>> >>> ZOO-Project PSC chair
>> >>>
>> >>>
>> >>>
>> >>> Le 21 juin 2013 à 10:22, Frans Thamura <frans at meruvian.org> a écrit :
>> >>>
>> >>> > Wow next zoo in v8
>> >>> >
>> >>> > That can easily become paas ready apps
>> >>> >
>> >>> > On Jun 21, 2013 3:12 PM, "Fenoy Gerald" <gerald.fenoy at geolabs.fr>
>> wrote:
>> >>> > Frans,
>> >>> > I forward this email to the ZOO-Discuss mailing list.
>> >>> >
>> >>> > 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 ?
>> >>> >
>> >>> > You can find some informations here : [1]
>> >>> >
>> >>> > 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.
>> >>> >
>> >>> > Waiting for your answer.
>> >>> > Best regards,
>> >>> >
>> >>> > Gérald Fenoy
>> >>> > ZOO-Project PSC Chair
>> >>> >
>> >>> > [1]
>> http://zoo-project.org/trac/wiki/ZOO_SoC_Ideas#ZOO-Kernelrelatedideas
>> >>> >
>> >>> > Le 15 juin 2013 à 04:54, Frans Thamura <frans at meruvian.org> a
>> écrit :
>> >>> >
>> >>> > > V8 is the chrome engine
>> >>> > >
>> >>> > > https://developers.google.com/v8/embed
>> >>> > >
>> >>> > > because this tutorial, we can embed in paas, and nodejs also run
>> on paas now
>> >>> > >
>> >>> > > nodejs is build on top of v8
>> >>> > >
>> >>> > >
>> >>> > > --
>> >>> > > Frans Thamura (曽志胜)
>> >>> > > Shadow Master and Lead Investor
>> >>> > > Meruvian.
>> >>> > > Integrated Hypermedia Java Solution Provider.
>> >>> > >
>> >>> > > Mobile: +628557888699
>> >>> > > Blog: http://blogs.mervpolis.com/roller/flatburger (id)
>> >>> > >
>> >>> > > FB: http://www.facebook.com/meruvian
>> >>> > > TW: http://www.twitter.com/meruvian / @meruvian
>> >>> > > Website: http://www.meruvian.org
>> >>> > >
>> >>> > > "We grow because we share the same belief."
>> >>> >
>> >>> > _______________________________________________
>> >>> > Zoo-discuss mailing list
>> >>> > Zoo-discuss at lists.osgeo.org
>> >>> > http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss
>> >>>
>> >>>
>> >>>
>> >>> _______________________________________________
>> >>> Zoo-discuss mailing list
>> >>>
>> >>> Zoo-discuss at lists.osgeo.org
>> >>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss
>> >>
>> >
>> > _______________________________________________
>> > Zoo-discuss mailing list
>> > Zoo-discuss at lists.osgeo.org
>> > http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss
>>
>>  _______________________________________________
> Zoo-discuss mailing list
> Zoo-discuss at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/zoo-discuss/attachments/20130621/2389a5b2/attachment.html>