September 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] fosdem 2015

by Stephan Eggermont

Santiage wrote: >Hi people!, Will we have room in next FOSDEM? I will put out a proposal for a devroom, yes. That is no guarantee that we will get one, the amount of space is limited. Stephan

Sept. 12, 2014

Re: [Pharo-dev] Zinc-rest URL matching

by Sven Van Caekenberghe

On 12 Sep 2014, at 12:23, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > Hi Sven, > > Le 12 sept. 2014 Ã 11:59, Sven Van Caekenberghe a Ã©crit : > >> Hi Christophe, >> >> On 12 Sep 2014, at 10:28, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: >> >>> Hi, >>> >>> I use Zinc-Rest and it works like a charm, really simple to quickly get something working. >>> I have a question about URL pattern matching that is used to dispatch request to the right handler. >>> I want to have following URLs: >>> /foo/* >>> /foo/latest >>> I defined 2 handlers with following patterns: >>> #('foo' '*') >>> #('foo' 'latest') >>> >>> I was expecting that the more precise handler was chosen but it was the generic handler (with '*'). Is there a way to do that? >>> It is not blocking because I can use the same handler to manage both patterns but I would prefer to have them separated as the semantic is not the same. >>> >>> Regards, >>> Christophe. >> >> My first answer would indeed also have been to handle both cases in one call (I did similar things in my projects). But now that you mention it, I think this can be fixed quite easily. Have a look at the following version: >> >> === >> Name: Zinc-REST-SvenVanCaekenberghe.16 >> Author: SvenVanCaekenberghe >> Time: 12 September 2014, 11:55:02.020483 am >> UUID: 6421d8be-c7c8-44fc-8958-121cc86ae93e >> Ancestors: Zinc-REST-SvenVanCaekenberghe.15 >> >> ZnCallHierarchyRestUriSpace>>#match: now uses #order to sort auto matched REST call subclasses - a lower order call will be matched before a higher order call. >> === >> >> By default, calls inherit order 50, to make move one call earlier in the matching process, override #order with a lower number. > > Indeed, it does the trick with only a few changes :) > I wonder if it would be a good idea to give a default lower priority (ex: 20) if the pattern ends with a '*'. It could be done in the order method. I think you will never had to override priority this way but it has a little CPU overhead. Hmm, I thought about other ways of sorting patterns, but they will all be quite complex. [ Also remember that from a design standpoint, #pattern is not external, only #match: is, as there could be other approaches to matching ]. The trick with #order is very simple and only has to be used when there is a actual conflict, which is quite seldom I think. I can think of more conflicts than the one you can up with /tasks /tasks/* /tasks/last /tasks/*/items/* /tasks/last/items/* /tasks/*/items/last What I mean is, it is not just the number of stars. [ More like the longest match ]. But if you would come up with something general enough I would be interested. BTW, REST API design is quite hard, we have discussion about this subject here every week. > Thanks for the quick feedback. It looks like functionality on-demand :) > > Christophe

Sept. 12, 2014

Re: [Pharo-dev] Zinc-rest URL matching

by Christophe Demarey

Hi Sven, Le 12 sept. 2014 Ã 11:59, Sven Van Caekenberghe a Ã©crit : > Hi Christophe, > > On 12 Sep 2014, at 10:28, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > >> Hi, >> >> I use Zinc-Rest and it works like a charm, really simple to quickly get something working. >> I have a question about URL pattern matching that is used to dispatch request to the right handler. >> I want to have following URLs: >> /foo/* >> /foo/latest >> I defined 2 handlers with following patterns: >> #('foo' '*') >> #('foo' 'latest') >> >> I was expecting that the more precise handler was chosen but it was the generic handler (with '*'). Is there a way to do that? >> It is not blocking because I can use the same handler to manage both patterns but I would prefer to have them separated as the semantic is not the same. >> >> Regards, >> Christophe. > > My first answer would indeed also have been to handle both cases in one call (I did similar things in my projects). But now that you mention it, I think this can be fixed quite easily. Have a look at the following version: > > === > Name: Zinc-REST-SvenVanCaekenberghe.16 > Author: SvenVanCaekenberghe > Time: 12 September 2014, 11:55:02.020483 am > UUID: 6421d8be-c7c8-44fc-8958-121cc86ae93e > Ancestors: Zinc-REST-SvenVanCaekenberghe.15 > > ZnCallHierarchyRestUriSpace>>#match: now uses #order to sort auto matched REST call subclasses - a lower order call will be matched before a higher order call. > === > > By default, calls inherit order 50, to make move one call earlier in the matching process, override #order with a lower number. Indeed, it does the trick with only a few changes :) I wonder if it would be a good idea to give a default lower priority (ex: 20) if the pattern ends with a '*'. It could be done in the order method. I think you will never had to override priority this way but it has a little CPU overhead. Thanks for the quick feedback. It looks like functionality on-demand :) Christophe

Sept. 12, 2014

Re: [Pharo-dev] Zinc-rest URL matching

by Christophe Demarey

Le 12 sept. 2014 Ã 10:50, Santiago Bragagnolo a Ã©crit : > > You may want to check this thread. > > http://forum.world.st/ANN-Teapot-0-8-micro-web-framework-tp4774449.html > > Hope it solves your needs :) Thanks, nice framework. Interesting to know

Sept. 12, 2014

fosdem 2015

by Santiago Bragagnolo

Hi people!, Will we have room in next FOSDEM?

Sept. 12, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40220 Home: https://github.com/pharo-project/pharo-core

Sept. 12, 2014

[pharo-project/pharo-core] 56d108: 40220

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 56d1088926e2b3f5602ee74771eb1d5f00e5b987 https://github.com/pharo-project/pharo-core/commit/56d1088926e2b3f5602ee747… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-12 (Fri, 12 Sep 2014) Changed paths: M Refactoring-Critics.package/RBSentNotImplementedRule.class/instance/running/checkMethod_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script220.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40220.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A System-CachingTests.package/DoubleLinkedListTests.class/README.md A System-CachingTests.package/DoubleLinkedListTests.class/definition.st A System-CachingTests.package/DoubleLinkedListTests.class/instance/testing/testAddAfterLink.st A System-CachingTests.package/DoubleLinkedListTests.class/instance/testing/testAddBeforeLink.st A System-CachingTests.package/DoubleLinkedListTests.class/instance/testing/testAddFirst.st A System-CachingTests.package/DoubleLinkedListTests.class/instance/testing/testAddLast.st A System-CachingTests.package/DoubleLinkedListTests.class/instance/testing/testCollect.st A System-CachingTests.package/DoubleLinkedListTests.class/instance/testing/testDo.st A System-CachingTests.package/DoubleLinkedListTests.class/instance/testing/testEmpty.st A System-CachingTests.package/DoubleLinkedListTests.class/instance/testing/testIncludes.st A System-CachingTests.package/DoubleLinkedListTests.class/instance/testing/testOne.st A System-CachingTests.package/DoubleLinkedListTests.class/instance/testing/testOneRemoveFirst.st A System-CachingTests.package/DoubleLinkedListTests.class/instance/testing/testOneRemoveLast.st A System-CachingTests.package/DoubleLinkedListTests.class/instance/testing/testReject.st A System-CachingTests.package/DoubleLinkedListTests.class/instance/testing/testReverseDo.st A System-CachingTests.package/DoubleLinkedListTests.class/instance/testing/testSelect.st A System-CachingTests.package/DoubleLinkedListTests.class/instance/testing/testThree.st A System-CachingTests.package/DoubleLinkedListTests.class/instance/testing/testThreeRemoveFirst.st A System-CachingTests.package/DoubleLinkedListTests.class/instance/testing/testThreeRemoveLast.st A System-CachingTests.package/DoubleLinkedListTests.class/instance/testing/testThreeRemoveLink.st A System-CachingTests.package/LRUCacheTests.class/README.md A System-CachingTests.package/LRUCacheTests.class/definition.st A System-CachingTests.package/LRUCacheTests.class/instance/accessing/newCache.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/test5kClasses.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/test6k.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testCustomWeight.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testEmpty.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testEnumeration.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testEviction.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testFactory.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testFactoryStyle.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testFibonacci.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testFixedAccess.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testOne.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testOneHit.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testOneHitTwice.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testPrimeFactors.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testRandomAccess.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testRemoveAll.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testRemoveOne.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testRemoveOneOfThree.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testTen.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testTenThreadSafe.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testThree.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testThreeHitSameOne.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testTwo.st A System-CachingTests.package/TTLCacheTests.class/README.md A System-CachingTests.package/TTLCacheTests.class/definition.st A System-CachingTests.package/TTLCacheTests.class/instance/accessing/newCache.st A System-CachingTests.package/TTLCacheTests.class/instance/testing/testExpiring.st A System-CachingTests.package/TTLCacheTests.class/instance/testing/testRemoveStaleValues.st Log Message: ----------- 40220 13901 move DoubleLinkedListTests, LRUCacheTests and TTLCacheTests from Tests https://pharo.fogbugz.com/f/cases/13901 13996 RBSentNotImplementedRule wrong https://pharo.fogbugz.com/f/cases/13996 http://files.pharo.org/image/40/40220.zip

Sept. 12, 2014

Re: [Pharo-dev] Zinc-rest URL matching

by Sven Van Caekenberghe

Hi Christophe, On 12 Sep 2014, at 10:28, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > Hi, > > I use Zinc-Rest and it works like a charm, really simple to quickly get something working. > I have a question about URL pattern matching that is used to dispatch request to the right handler. > I want to have following URLs: > /foo/* > /foo/latest > I defined 2 handlers with following patterns: > #('foo' '*') > #('foo' 'latest') > > I was expecting that the more precise handler was chosen but it was the generic handler (with '*'). Is there a way to do that? > It is not blocking because I can use the same handler to manage both patterns but I would prefer to have them separated as the semantic is not the same. > > Regards, > Christophe. My first answer would indeed also have been to handle both cases in one call (I did similar things in my projects). But now that you mention it, I think this can be fixed quite easily. Have a look at the following version: === Name: Zinc-REST-SvenVanCaekenberghe.16 Author: SvenVanCaekenberghe Time: 12 September 2014, 11:55:02.020483 am UUID: 6421d8be-c7c8-44fc-8958-121cc86ae93e Ancestors: Zinc-REST-SvenVanCaekenberghe.15 ZnCallHierarchyRestUriSpace>>#match: now uses #order to sort auto matched REST call subclasses - a lower order call will be matched before a higher order call. === By default, calls inherit order 50, to make move one call earlier in the matching process, override #order with a lower number. Thanks for the feedback, this is really helpful. HTH, Sven

Sept. 12, 2014

[pharo-project/pharo-core] 0964b9: 40219

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 0964b98329abb623c8f85c25e414009a5ec4b2da https://github.com/pharo-project/pharo-core/commit/0964b98329abb623c8f85c25… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-12 (Fri, 12 Sep 2014) Changed paths: M Refactoring-Critics.package/RBImplementedNotSentRule.class/definition.st A Refactoring-Critics.package/RBImplementedNotSentRule.class/instance/cache/literals.st A Refactoring-Critics.package/RBImplementedNotSentRule.class/instance/private/addLiteral_.st M Refactoring-Critics.package/RBImplementedNotSentRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBImplementedNotSentRule.class/instance/running/resetResult.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script219.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40219.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Announcements.package/MethodRecategorized.class/instance/accessing/methodRecategorized_.st M System-Announcements.package/MethodRemoved.class/instance/accessing/methodRemoved_.st Log Message: ----------- 40219 13993 remove two undeclared in System-Announcemetns https://pharo.fogbugz.com/f/cases/13993 13990 RBImplementedNotSentRule slow https://pharo.fogbugz.com/f/cases/13990 http://files.pharo.org/image/40/40219.zip

Sept. 12, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40219 Home: https://github.com/pharo-project/pharo-core

Sept. 12, 2014