- Pharo-users - lists.pharo.org

ptsd rage

by Robert Withers

I need to apologize for all my dread behavior. Here is the reason, and I am on service-connected disability. Current diagnosis is Complex PTSD. Sorry about all my sturm und drang. http://www.ptsd.va.gov/public/problems/anger-and-trauma.asp Sincerely, Robert

Dec. 17, 2016

Re: [Pharo-users] NeoJSON

by stepharong

> Strange. > > In Neo-JSON-Core-SvenVanCaekenberghe.37 in the class comment of > NeoJSONMapper last paragraph before the examples. sure I just meant that it was not visible enough. We should add for example XXX >> neoJsonMapping: aMapper aMapper for: self do: [ :mapping | mapping mapInstVars: #(#title #kind #hasDoc #grade #stars #isCollectorEdition #paidPrice #language #zone)] > >> Now do you have an idea why I got this other missing class mapping for >> bytestring? > > You must have done something wrong ;-) > > NeoJSONWriter toString: { 'string'. #symbol. 1. Float pi }. > > '["string","symbol",1,3.141592653589793]' I do not think so because my objects totally stupid. So this is why I was surprised. here are two exampleKlonoa <sampleInstance> ^ self new title: 'Klonoa'; ps2; threeStar; grade: '(16/15)'; paidPrice: 1 exampleWildArm <sampleInstance> ^ self new title: 'Wild Arm'; ps2; threeStar; grade: '(16/15)'; paidPrice: 1 only strings, numbers and symbols. this ByteString looked strange. > >> Stef >> >> On Fri, 16 Dec 2016 15:25:40 +0100, Sven Van Caekenberghe >> <sven(a)stfx.eu> wrote: >> >>> >>>> On 16 Dec 2016, at 15:23, stepharong <stepharong(a)free.fr> wrote: >>>> >>>> Ok I see. >>>> >>>> I was doing >>>> >>>> GameCollection >> neoJsonOn: neoJSONWriter >>>> >>>> neoJSONWriter >>>> writeObject: games >>>> >>>> >>>> GameItem >> neoJsonOn: neoJSONWriter >>>> self class instanceVariables >>>> do: [ :each | >>>> neoJSONWriter writeObject: (self instVarNamed: each) ] >>>> >>>> >>>> Now it did not work because byteString is not covered and I found >>>> that strange. >>>> >>>> I will use your solution. >>>> >>>> I read the section 5 before so there is something missing there. >>>> I will see how I can add an example. >>>> >>>> May be we should improve the class comment of mapper stating this >>>> class methods. >>> >>> It is right there, in NeoJSONMapper's class comment >>> >>> ... >>> A mapping can be specified explicitely on a mapper, or can be resolved >>> using the #neoJsonMapping: class method. >>> ... >>> >>> This is the superclass of both NeoJSONReader and NeoJSONWriter. >>> >>> But we should add it to the book chapter too. >>> >>>> Stef >>> >> >> >> -- >> Using Opera's mail client: http://www.opera.com/mail/ > -- Using Opera's mail client: http://www.opera.com/mail/

Dec. 16, 2016

Re: [Pharo-users] NeoJSON

by Sven Van Caekenberghe

> On 16 Dec 2016, at 15:47, stepharong <stepharong(a)free.fr> wrote: > > Ok it works :) Good. > And I read the class comment but I do not see it. Strange. In Neo-JSON-Core-SvenVanCaekenberghe.37 in the class comment of NeoJSONMapper last paragraph before the examples. > Now do you have an idea why I got this other missing class mapping for bytestring? You must have done something wrong ;-) NeoJSONWriter toString: { 'string'. #symbol. 1. Float pi }. '["string","symbol",1,3.141592653589793]' > Stef > > On Fri, 16 Dec 2016 15:25:40 +0100, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> >>> On 16 Dec 2016, at 15:23, stepharong <stepharong(a)free.fr> wrote: >>> >>> Ok I see. >>> >>> I was doing >>> >>> GameCollection >> neoJsonOn: neoJSONWriter >>> >>> neoJSONWriter >>> writeObject: games >>> >>> >>> GameItem >> neoJsonOn: neoJSONWriter >>> self class instanceVariables >>> do: [ :each | >>> neoJSONWriter writeObject: (self instVarNamed: each) ] >>> >>> >>> Now it did not work because byteString is not covered and I found that strange. >>> >>> I will use your solution. >>> >>> I read the section 5 before so there is something missing there. >>> I will see how I can add an example. >>> >>> May be we should improve the class comment of mapper stating this class methods. >> >> It is right there, in NeoJSONMapper's class comment >> >> ... >> A mapping can be specified explicitely on a mapper, or can be resolved using the #neoJsonMapping: class method. >> ... >> >> This is the superclass of both NeoJSONReader and NeoJSONWriter. >> >> But we should add it to the book chapter too. >> >>> Stef >> > > > -- > Using Opera's mail client: http://www.opera.com/mail/

Dec. 16, 2016

Re: [Pharo-users] NeoJSON

by stepharong

Ok it works :) And I read the class comment but I do not see it. Now do you have an idea why I got this other missing class mapping for bytestring? Stef On Fri, 16 Dec 2016 15:25:40 +0100, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> On 16 Dec 2016, at 15:23, stepharong <stepharong(a)free.fr> wrote: >> >> Ok I see. >> >> I was doing >> >> GameCollection >> neoJsonOn: neoJSONWriter >> >> neoJSONWriter >> writeObject: games >> >> >> GameItem >> neoJsonOn: neoJSONWriter >> self class instanceVariables >> do: [ :each | >> neoJSONWriter writeObject: (self instVarNamed: each) ] >> >> >> Now it did not work because byteString is not covered and I found that >> strange. >> >> I will use your solution. >> >> I read the section 5 before so there is something missing there. >> I will see how I can add an example. >> >> May be we should improve the class comment of mapper stating this class >> methods. > > It is right there, in NeoJSONMapper's class comment > > ... > A mapping can be specified explicitely on a mapper, or can be resolved > using the #neoJsonMapping: class method. > ... > > This is the superclass of both NeoJSONReader and NeoJSONWriter. > > But we should add it to the book chapter too. > >> Stef > -- Using Opera's mail client: http://www.opera.com/mail/

Dec. 16, 2016

Re: [Pharo-users] NeoJSON

by Sven Van Caekenberghe

> On 16 Dec 2016, at 15:23, stepharong <stepharong(a)free.fr> wrote: > > Ok I see. > > I was doing > > GameCollection >> neoJsonOn: neoJSONWriter > > neoJSONWriter > writeObject: games > > > GameItem >> neoJsonOn: neoJSONWriter > self class instanceVariables > do: [ :each | > neoJSONWriter writeObject: (self instVarNamed: each) ] > > > Now it did not work because byteString is not covered and I found that strange. > > I will use your solution. > > I read the section 5 before so there is something missing there. > I will see how I can add an example. > > May be we should improve the class comment of mapper stating this class methods. It is right there, in NeoJSONMapper's class comment ... A mapping can be specified explicitely on a mapper, or can be resolved using the #neoJsonMapping: class method. ... This is the superclass of both NeoJSONReader and NeoJSONWriter. But we should add it to the book chapter too. > Stef

Dec. 16, 2016

Re: [Pharo-users] NeoJSON

by stepharong

Ok I see. I was doing GameCollection >> neoJsonOn: neoJSONWriter neoJSONWriter writeObject: games GameItem >> neoJsonOn: neoJSONWriter self class instanceVariables do: [ :each | neoJSONWriter writeObject: (self instVarNamed: each) ] Now it did not work because byteString is not covered and I found that strange. I will use your solution. I read the section 5 before so there is something missing there. I will see how I can add an example. May be we should improve the class comment of mapper stating this class methods. Stef

Dec. 16, 2016

Re: [Pharo-users] NeoJSON

by Sven Van Caekenberghe

> On 16 Dec 2016, at 15:10, stepharong <stepharong(a)free.fr> wrote: > > I looked at the Neo code and I do not see how I can specify a mapping at the class level > because I cannot control the json writer creation. See my previous message (sent at the same time ;-) << add it to the class side of your model objects as #neoJsonMapping: (search for implementors as examples). >> > So I should probably shortcut everything at the neoJsonOn: level. > > Stef > > >> Hi sven >> >> I'm trying to adapt the teapot library example to get a simple item collector (as a project for a future book) and >> so that I can learn and use it for my PS2/PS3 game collection :) >> >> Now when I set up teapot to emit JSON I get an NeoJSONMappingNotFound >> In the library example attila does not manipulate objects but dictionaries. >> So I imagine that I have to do something :) >> I read the NeoJSON chapter but I did not find the solution. >> >> Should I implement >> neoJsonOn: >> on my domain? >> >> Stef >> > > > -- > Using Opera's mail client: http://www.opera.com/mail/ >

Dec. 16, 2016

Re: [Pharo-users] NeoJSON

by Sven Van Caekenberghe

Stef, > On 16 Dec 2016, at 15:00, stepharong <stepharong(a)free.fr> wrote: > > Hi sven > > I'm trying to adapt the teapot library example to get a simple item collector (as a project for a future book) and > so that I can learn and use it for my PS2/PS3 game collection :) > > Now when I set up teapot to emit JSON I get an NeoJSONMappingNotFound > In the library example attila does not manipulate objects but dictionaries. > So I imagine that I have to do something :) > I read the NeoJSON chapter but I did not find the solution. > > Should I implement > neoJsonOn: > on my domain? Section 5 of https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… explains most of this. You either add the mapping to the writer, builder style, or you add it to the class side of your model objects as #neoJsonMapping: (search for implementors as examples). I see that this second aspect is not well explained in the book. In the simplest case, the following is enough: neoJsonMapping: mapper mapper for: self do: [ :mapping | mapping mapInstVars: #(id width height data) ] But is gets a bit more complicated with inheritance. In a last resort you could also overwrite #neoJsonOn: Now, this is all for the writer side. Reading is harder because JSON has no type info (that what STON adds, among others), so you have to tell the reader what (static) type you want the parser to create. This is based on the same mapping. This is what #nextAs: does. If you have a more complex graph with collection values, you need to type all of them 'statically'. There are some examples in the unit tests. Sven > Stef > > -- > Using Opera's mail client: http://www.opera.com/mail/ >

Dec. 16, 2016

Re: [Pharo-users] NeoJSON

by stepharong

I looked at the Neo code and I do not see how I can specify a mapping at the class level because I cannot control the json writer creation. So I should probably shortcut everything at the neoJsonOn: level. Stef > Hi sven > > I'm trying to adapt the teapot library example to get a simple item > collector (as a project for a future book) and > so that I can learn and use it for my PS2/PS3 game collection :) > > Now when I set up teapot to emit JSON I get an NeoJSONMappingNotFound > In the library example attila does not manipulate objects but > dictionaries. > So I imagine that I have to do something :) > I read the NeoJSON chapter but I did not find the solution. > > Should I implement > neoJsonOn: > on my domain? > > Stef > -- Using Opera's mail client: http://www.opera.com/mail/

Dec. 16, 2016

Re: [Pharo-users] real world pharo web application set ups

by phil＠highoctane.be

I have been doing lots of Tomcat as well and helped some people at Orange scale some of their mobile provisioning stuff. It scales. But one would scale Pharo just the same. I remember some AJP module for Pharo/Squeak and http://book.seaside.st/book/advanced/deployment/deployment-apache/mod-proxy… Lets of parms in there but can help scale things and do session affinity. https://tomcat.apache.org/tomcat-7.0-doc/config/ajp.html Phil On Fri, Dec 16, 2016 at 1:50 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > On 16 Dec 2016, at 10:41, Norbert Hartl <norbert(a)hartl.name> wrote: > > We are talking about really high numbers of requests/s. The odds you are > getting in this kind of scaling trouble are usually close to zero. It means > you need to generate an application that has really many users. Most > projects we know end up using a single image for everything. > > > amen to everything, but this in particular. 1000 /concurrent/ requests are > a HUGE amount of requests most applications will never need. > > Remember concurrent does not means simultaneous but in the same lapseâ¦ > which means in any fraction of time you measures you can count 1000 > requests being processed (no matter if thatâs 1ms, 1s or 1m)â¦ when I was > designing web-applications all the time, the count I usually was doing was: > the number of users I expect to have, grouped by time-picks then I was > dividing that per 50/s (this was an âobscureâ heuristic I got from some > even more obscure general observation that have much to do with the fact > that people spend much more time looking a monitor than clicking a mouse). > > For example: to serve an application to 1000 users, > > - letâs consider 80% are connected at pick times = 800 users who I need to > serve > - = roughly 40 requests per secondâ¦ > > so in general a couple of tomcats would be ok (because at the time I was > working in java). > â¦ or 4 pharos. > > now, as I always said at the time: this are estimations that are meant to > calme the stress of customers (the ones who pays for the projects) or my > project managers (who didnât know much about systems anyway)â¦ > and they just worked as âpain-killersâ because since I really cannot know > how much will take a request I cannot measure anything. > Even worst: Iâm assuming all request take same time, which absolutely a > non sense. > > But well, since people (both customers and managers) always made that > question, I made up that number based in my own observation (20 years of > experience, not so bad) that âin general, a Tomcat can handle about 40 > req/s and Seaside can handle something around 15â¦ and you always need to > calculate a bit more because of murphyâs lawâ. Fun fact: the estimation was > in general correct :P > > In conclusion: if you *really* need to serve 1000 concurrent users, youâll > probably have the budget to make it right :) > > Esteban >

Dec. 16, 2016