April 2013 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Zinc GET request with body in the request.

by Sven Van Caekenberghe

On 23 Apr 2013, at 21:42, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 23.04.2013 um 21:30 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > >> >> On 23 Apr 2013, at 21:21, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> >>> Am 23.04.2013 um 20:52 schrieb Camillo Bruni <camillobruni(a)gmail.com>: >>> >>>> I just had a quick peek, shouldn't that be all post requests? >>>> >>>> get does not support a body, you have to pass everything as url parameters. >>>> >>> Can you elaborate on this? Why does GET not "support" a body? There is just no explicit mentioning of it in the rfc but on the same track there is no exclusion for that scenario. >> >> Technically you can include a body with a GET or any method, but it should not have a semantic meaning, according to Roy Fielding: >> >> http://tech.groups.yahoo.com/group/rest-discuss/message/9962 >> > Well, there is just the statement of Roy Fielding that it isn't useful but no explanation. I would be very interested in a proper answer. I can follow the line of reasoning not to include a body in a GET request. The situation in case of JSON is just that is less awkward to use for complex parameterization with JSON instead of putting everything in query parameters. So until there is a good explanation why you shouldn't I would be all for it :) Yeah, it is not really forbidden and it can be useful, so even if it is pretty uncommon, it should be allowed/supported, in a pinch. > Norbert >> ;-) >> >>> Norbert >>>> On 2013-04-23, at 20:41, Paul DeBruicker <pdebruic(a)gmail.com> wrote: >>>>> I'm making an elasticsearch client and they utilize JSON bodies in the >>>>> GET requests to their server to search and do other things. An example >>>>> of that is the second code block here: >>>>> >>>>> http://www.elasticsearch.org/guide/reference/api/search/ >>>>> >>>>> >>>>> Is there a way to include a body with a GET request using Zinc? >>>>> >>>>> >>>>> Making this: >>>>> >>>>> ZnClient>>#get:contents: >>>>> "Execute an HTTP GET request on url with the contents in a body and >>>>> return the response #contents." >>>>> >>>>> ^ self >>>>> url: url; >>>>> contents: object; >>>>> get >>>>> >>>>> >>>>> (unsurprisingly) doesn't work right away. >>>>> >>>>> >>>>> In elasticsearch it is possible to make a URI request for searching but >>>>> it is a more limited interface than including the JSON body. >>>>> >>>>> >>>>> Thanks >>>>> >>>>> Paul >>>>> >>>> >>>> >>> >>> >> >> > >

April 23, 2013

Re: [Pharo-users] Zinc GET request with body in the request.

by Norbert Hartl

Am 23.04.2013 um 21:30 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > On 23 Apr 2013, at 21:21, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> Am 23.04.2013 um 20:52 schrieb Camillo Bruni <camillobruni(a)gmail.com>: >> >>> I just had a quick peek, shouldn't that be all post requests? >>> >>> get does not support a body, you have to pass everything as url parameters. >>> >> Can you elaborate on this? Why does GET not "support" a body? There is just no explicit mentioning of it in the rfc but on the same track there is no exclusion for that scenario. > > Technically you can include a body with a GET or any method, but it should not have a semantic meaning, according to Roy Fielding: > > http://tech.groups.yahoo.com/group/rest-discuss/message/9962 > Well, there is just the statement of Roy Fielding that it isn't useful but no explanation. I would be very interested in a proper answer. I can follow the line of reasoning not to include a body in a GET request. The situation in case of JSON is just that is less awkward to use for complex parameterization with JSON instead of putting everything in query parameters. So until there is a good explanation why you shouldn't I would be all for it :) Norbert > ;-) > >> Norbert >>> On 2013-04-23, at 20:41, Paul DeBruicker <pdebruic(a)gmail.com> wrote: >>>> I'm making an elasticsearch client and they utilize JSON bodies in the >>>> GET requests to their server to search and do other things. An example >>>> of that is the second code block here: >>>> >>>> http://www.elasticsearch.org/guide/reference/api/search/ >>>> >>>> >>>> Is there a way to include a body with a GET request using Zinc? >>>> >>>> >>>> Making this: >>>> >>>> ZnClient>>#get:contents: >>>> "Execute an HTTP GET request on url with the contents in a body and >>>> return the response #contents." >>>> >>>> ^ self >>>> url: url; >>>> contents: object; >>>> get >>>> >>>> >>>> (unsurprisingly) doesn't work right away. >>>> >>>> >>>> In elasticsearch it is possible to make a URI request for searching but >>>> it is a more limited interface than including the JSON body. >>>> >>>> >>>> Thanks >>>> >>>> Paul >>>> >>> >>> >> >> > >

April 23, 2013

Re: [Pharo-users] Zinc GET request with body in the request.

by Norbert Hartl

Am 23.04.2013 um 21:21 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > Paul, > > Well, it is against the spec IMHO: there should be no body with GET or HEAD. > Well, it is a "must not" for HEAD and a "not mentioned at all" for GET. The "should not" use a body for GET is meant that a GET request should only include query parameters or paramterization of a retrieval action. So it is pretty unclear what should be done. I translate the same thing as: A request body for GET request is ok if the body contains only query parameters and does not alter system state (just be idempotent). The same problem goes by "simply" choosing POST for the same request. The interpretation of the URI is different for GET and POST. In case of elasticsearch you really query the entity that is in the URI. For POST it isn't. Norbert > That is why the body is cleared in ZnClient>>#method: in those cases (ZnClient is meant to be reused for multiple requests). > > But by using a small detour it is possible: > > ZnClient new > logToTranscript; > url: 'http://zn.stfx.eu/echo'; > method: #GET; > contents: 'Foobar'; > execute. > > If you inspect the reply to /echo you will notice that the server acknowledges receiving an entity. This should do the trick. > > HTH, > > Sven > > PS: You can use ZnClient>>#contentWriter: to convert from Smalltalk to JSON automagically... > > On 23 Apr 2013, at 21:02, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > >> I don't know what should be but if you substitute -XPOST or just -POST >> for the -XGET then the search fails and you get no results. the -X just >> forces curl to use the HTTP method that follows. >> >> >> It does seem to be contrary to the HTTP spec but I'm not sure of that >> either. >> >> >> >> >> >> On 04/23/2013 11:52 AM, Camillo Bruni wrote: >>> I just had a quick peek, shouldn't that be all post requests? >>> >>> get does not support a body, you have to pass everything as url parameters. >>> >>> On 2013-04-23, at 20:41, Paul DeBruicker <pdebruic(a)gmail.com> wrote: >>>> I'm making an elasticsearch client and they utilize JSON bodies in the >>>> GET requests to their server to search and do other things. An example >>>> of that is the second code block here: >>>> >>>> http://www.elasticsearch.org/guide/reference/api/search/ >>>> >>>> >>>> Is there a way to include a body with a GET request using Zinc? >>>> >>>> >>>> Making this: >>>> >>>> ZnClient>>#get:contents: >>>> "Execute an HTTP GET request on url with the contents in a body and >>>> return the response #contents." >>>> >>>> ^ self >>>> url: url; >>>> contents: object; >>>> get >>>> >>>> >>>> (unsurprisingly) doesn't work right away. >>>> >>>> >>>> In elasticsearch it is possible to make a URI request for searching but >>>> it is a more limited interface than including the JSON body. >>>> >>>> >>>> Thanks >>>> >>>> Paul >>>> >>> >>> >> >> > >

April 23, 2013

Re: [Pharo-users] Zinc GET request with body in the request.

by Sven Van Caekenberghe

On 23 Apr 2013, at 21:21, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 23.04.2013 um 20:52 schrieb Camillo Bruni <camillobruni(a)gmail.com>: > >> I just had a quick peek, shouldn't that be all post requests? >> >> get does not support a body, you have to pass everything as url parameters. >> > Can you elaborate on this? Why does GET not "support" a body? There is just no explicit mentioning of it in the rfc but on the same track there is no exclusion for that scenario. Technically you can include a body with a GET or any method, but it should not have a semantic meaning, according to Roy Fielding: http://tech.groups.yahoo.com/group/rest-discuss/message/9962 ;-) > Norbert >> On 2013-04-23, at 20:41, Paul DeBruicker <pdebruic(a)gmail.com> wrote: >>> I'm making an elasticsearch client and they utilize JSON bodies in the >>> GET requests to their server to search and do other things. An example >>> of that is the second code block here: >>> >>> http://www.elasticsearch.org/guide/reference/api/search/ >>> >>> >>> Is there a way to include a body with a GET request using Zinc? >>> >>> >>> Making this: >>> >>> ZnClient>>#get:contents: >>> "Execute an HTTP GET request on url with the contents in a body and >>> return the response #contents." >>> >>> ^ self >>> url: url; >>> contents: object; >>> get >>> >>> >>> (unsurprisingly) doesn't work right away. >>> >>> >>> In elasticsearch it is possible to make a URI request for searching but >>> it is a more limited interface than including the JSON body. >>> >>> >>> Thanks >>> >>> Paul >>> >> >> > >

April 23, 2013

Re: [Pharo-users] Zinc GET request with body in the request.

by Norbert Hartl

Am 23.04.2013 um 20:52 schrieb Camillo Bruni <camillobruni(a)gmail.com>: > I just had a quick peek, shouldn't that be all post requests? > > get does not support a body, you have to pass everything as url parameters. > Can you elaborate on this? Why does GET not "support" a body? There is just no explicit mentioning of it in the rfc but on the same track there is no exclusion for that scenario. Norbert > On 2013-04-23, at 20:41, Paul DeBruicker <pdebruic(a)gmail.com> wrote: >> I'm making an elasticsearch client and they utilize JSON bodies in the >> GET requests to their server to search and do other things. An example >> of that is the second code block here: >> >> http://www.elasticsearch.org/guide/reference/api/search/ >> >> >> Is there a way to include a body with a GET request using Zinc? >> >> >> Making this: >> >> ZnClient>>#get:contents: >> "Execute an HTTP GET request on url with the contents in a body and >> return the response #contents." >> >> ^ self >> url: url; >> contents: object; >> get >> >> >> (unsurprisingly) doesn't work right away. >> >> >> In elasticsearch it is possible to make a URI request for searching but >> it is a more limited interface than including the JSON body. >> >> >> Thanks >> >> Paul >> > >

April 23, 2013

Re: [Pharo-users] Zinc GET request with body in the request.

by Sven Van Caekenberghe

Paul, Well, it is against the spec IMHO: there should be no body with GET or HEAD. That is why the body is cleared in ZnClient>>#method: in those cases (ZnClient is meant to be reused for multiple requests). But by using a small detour it is possible: ZnClient new logToTranscript; url: 'http://zn.stfx.eu/echo'; method: #GET; contents: 'Foobar'; execute. If you inspect the reply to /echo you will notice that the server acknowledges receiving an entity. This should do the trick. HTH, Sven PS: You can use ZnClient>>#contentWriter: to convert from Smalltalk to JSON automagically... On 23 Apr 2013, at 21:02, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > I don't know what should be but if you substitute -XPOST or just -POST > for the -XGET then the search fails and you get no results. the -X just > forces curl to use the HTTP method that follows. > > > It does seem to be contrary to the HTTP spec but I'm not sure of that > either. > > > > > > On 04/23/2013 11:52 AM, Camillo Bruni wrote: >> I just had a quick peek, shouldn't that be all post requests? >> >> get does not support a body, you have to pass everything as url parameters. >> >> On 2013-04-23, at 20:41, Paul DeBruicker <pdebruic(a)gmail.com> wrote: >>> I'm making an elasticsearch client and they utilize JSON bodies in the >>> GET requests to their server to search and do other things. An example >>> of that is the second code block here: >>> >>> http://www.elasticsearch.org/guide/reference/api/search/ >>> >>> >>> Is there a way to include a body with a GET request using Zinc? >>> >>> >>> Making this: >>> >>> ZnClient>>#get:contents: >>> "Execute an HTTP GET request on url with the contents in a body and >>> return the response #contents." >>> >>> ^ self >>> url: url; >>> contents: object; >>> get >>> >>> >>> (unsurprisingly) doesn't work right away. >>> >>> >>> In elasticsearch it is possible to make a URI request for searching but >>> it is a more limited interface than including the JSON body. >>> >>> >>> Thanks >>> >>> Paul >>> >> >> > >

April 23, 2013

Re: [Pharo-users] Terminating a Process when an object dies

by Luc Fabresse

Hi all, @Sven, yes of course I forgot the WeakArray to save the hard ref in my previous explanation. 2013/4/23 Igor Stasenko <siguctua(a)gmail.com> > On 23 April 2013 18:02, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Igor Stasenko wrote > >> but what you expecting? > >> you refer to 'self' multiple times. sure thing it cannot be GC-ed, > >> neither process will die because > >> of plenty of references on stack. > >> Even block closure which you creating for fork will have home context > >> which keeps reference to 'self', > >> e.g. receiver. > > > > I'm expecting magic apparently because I am stupid when it comes to > > processes ;) I changed all the "self"s to array first, which also didn't > > work, but then I read your statement about the home context... > > > > Luc's class-side trick seems to work: > > Timer>>start > > > > | array | > > array := WeakArray with: self. > > process := self class createProcessFor: array. "tried passing > self here, > > but it seemed to keep the process around" > > > of course, because the home context (will be the method below) of > closure captures method's arguments, > and holding them strongly.. > > Timer class>>createProcessFor: aWeakArray > > > > [ [ aWeakArray first notNil ] whileTrue: [ > > | timer | > > aWeakArray first interval asDelay wait. > > "We have to check again if the timer was garbage > collected during the > > wait" > > aWeakArray first ifNotNil: [ > > aWeakArray first value: aWeakArray first value + > 1. > > aWeakArray first announcer announce: > (TimerValueChanged to: aWeakArray > > first value) ] ] ] fork. > > > > Wow, it would seem that an object using a process internally that is only > > valid when the object is around is a fairly common use case. I can't > believe > > how complicated this is :/ > > > it is not apparent to me why this is common use case. :) > > you can also simply pass a copy of 'self' to process. > as long as copy accessing same announcer, your ticker process will > work perfectly. > then all you would need to do is: > > | copy | > copy := self copy. > @Igor. It will not work here I think. because you make the shallow copy before initializing the process and the finalize message is then sent to the copy. as Sven proposed, a WeakArray would be good but I never deeply test it. Anyway, I always fight with the finalization mechanism. With Noury we wrote an ActiveObject class some time ago that has an internal process that is stopped and the activeobject is finalized. The only thing is to be **really** carreful when giving the block to the ActiveObject to not introduce references. Here one of the test case that is green: testDoesStopBlockUponFinalizationForLowestPriority |counter startSemaphore finalizationSemaphore process | counter := 0. startSemaphore := Semaphore new. finalizationSemaphore := Semaphore new. activeObject := ActiveObject do: [ startSemaphore signal. [(Delay forMilliseconds: 50) wait]repeat ] ensure: [ counter := 1. finalizationSemaphore signal. ]. activeObject priority: Processor lowestPriority; start. self deny: (startSemaphore waitTimeoutSeconds: 2). process := activeObject process. activeObject := nil. Smalltalk garbageCollect. self deny: (finalizationSemaphore waitTimeoutSeconds: 2). self assert: counter = 1. self assert: process isTerminated Here the whole code: MCHttpRepository location: 'http://car.mines-douai.fr/squeaksource/ReusableBricks' user: '' password: '' Luc > process := self class createProcessFor: copy. > WeakRegistry default add: self executor: copy. > > and implement: > > finalize > process terminate. > process := nil. > > > Then createProcessFor: will be simple: > > Timer class>>createProcessFor: timer > [ > [ timer wait. " make Demeter a bit happier" > timer tick. "this should increment counter and announce > TimerValueChanged, > like that we're not make Demeter unhappy" > ] whileTrue ] fork. > > (actually , to make mr.Demeter completely happy, i would do > [ timer waitAndTick ] whileTrue. > ) > > and, tick, will be something like that: > > tick > process ifNil: [ ^ false ]. > self incrementCounter. > self announce: (MyGreatAnnouncement with: whatever). > ^ true. > > cheerz :) > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: > http://forum.world.st/Terminating-a-Process-when-an-object-dies-tp4683036p4… > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > > > -- > Best regards, > Igor Stasenko. > >

April 23, 2013

Re: [Pharo-users] Zinc GET request with body in the request.

by Paul DeBruicker

I don't know what should be but if you substitute -XPOST or just -POST for the -XGET then the search fails and you get no results. the -X just forces curl to use the HTTP method that follows. It does seem to be contrary to the HTTP spec but I'm not sure of that either. On 04/23/2013 11:52 AM, Camillo Bruni wrote: > I just had a quick peek, shouldn't that be all post requests? > > get does not support a body, you have to pass everything as url parameters. > > On 2013-04-23, at 20:41, Paul DeBruicker <pdebruic(a)gmail.com> wrote: >> I'm making an elasticsearch client and they utilize JSON bodies in the >> GET requests to their server to search and do other things. An example >> of that is the second code block here: >> >> http://www.elasticsearch.org/guide/reference/api/search/ >> >> >> Is there a way to include a body with a GET request using Zinc? >> >> >> Making this: >> >> ZnClient>>#get:contents: >> "Execute an HTTP GET request on url with the contents in a body and >> return the response #contents." >> >> ^ self >> url: url; >> contents: object; >> get >> >> >> (unsurprisingly) doesn't work right away. >> >> >> In elasticsearch it is possible to make a URI request for searching but >> it is a more limited interface than including the JSON body. >> >> >> Thanks >> >> Paul >> > >

April 23, 2013

Re: [Pharo-users] Zinc GET request with body in the request.

by Camillo Bruni

I just had a quick peek, shouldn't that be all post requests? get does not support a body, you have to pass everything as url parameters. On 2013-04-23, at 20:41, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > I'm making an elasticsearch client and they utilize JSON bodies in the > GET requests to their server to search and do other things. An example > of that is the second code block here: > > http://www.elasticsearch.org/guide/reference/api/search/ > > > Is there a way to include a body with a GET request using Zinc? > > > Making this: > > ZnClient>>#get:contents: > "Execute an HTTP GET request on url with the contents in a body and > return the response #contents." > > ^ self > url: url; > contents: object; > get > > > (unsurprisingly) doesn't work right away. > > > In elasticsearch it is possible to make a URI request for searching but > it is a more limited interface than including the JSON body. > > > Thanks > > Paul >

April 23, 2013

Re: [Pharo-users] Terminating a Process when an object dies

by Sean P. DeNigris

Igor Stasenko wrote > it is not apparent to me why this is common use case. :) In the sense that Smalltalk is prototype Dynabook software, part of the purpose of which is to do simulations ;) Also, I've seen this come up quite a bit and usually the suggestion is to hijack Morphic stepping, which seems to me like too ugly a hack. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Terminating-a-Process-when-an-object-dies-tp4683036p4… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 23, 2013