ruote log_2010-12-03

2010-12-03 07:15:31 utc jmettraux tosch_le: hello
2010-12-03 07:16:14 utc tosch_le hi!
2010-12-03 07:16:47 utc tosch_le sorry for being away so long, had some holidays the week before last and was ill the last days…
2010-12-03 07:17:02 utc jmettraux no worries, are you feeling better ?
2010-12-03 07:17:16 utc tosch_le not really :-(
2010-12-03 07:17:41 utc tosch_le but there's too much to do. and i'm looking for a new job, my boxx can't afford me anymore :-(
2010-12-03 07:17:48 utc tosch_le s/boxx/boss/
2010-12-03 07:18:02 utc jmettraux oh really ?
2010-12-03 07:18:15 utc tosch_le really.
2010-12-03 07:57:46 utc jfding Hi, all, one question of ruote
2010-12-03 07:57:59 utc tosch_le hi jfding!
2010-12-03 07:58:03 utc jmettraux jfding: hi
2010-12-03 07:58:04 utc jfding how to define a process to do sth. routinely, like cron
2010-12-03 07:58:27 utc jfding e.g. do one thing at 9am every day
2010-12-03 07:58:32 utc tosch_le use cron ;-)
2010-12-03 07:58:40 utc jmettraux http://ruote.rubyforge.org/expressions.html http://ruote.rubyforge.org/exp/cron.html
2010-12-03 07:58:59 utc jfding oh, I'll read it at once
2010-12-03 07:59:39 utc jfding have had a glance, I think I have found the answer
2010-12-03 07:59:49 utc jfding thanks you guys:) so nice
2010-12-03 08:00:16 utc jmettraux you're welcome
2010-12-03 08:06:18 utc jmettraux jfding: you're in Intel ?
2010-12-03 08:06:44 utc jfding yes
2010-12-03 08:07:01 utc jmettraux you guys are using Ruby ? Nice !
2010-12-03 08:07:19 utc jfding yes, we are very glad to use ruote, :)
2010-12-03 08:07:29 utc jfding actually, the MeeGo project
2010-12-03 08:07:37 utc jmettraux oh really ? Ah understood !
2010-12-03 08:07:42 utc jfding for the building infrastructure things
2010-12-03 08:08:35 utc jfding wiki.meego.com/BOSS :)
2010-12-03 08:08:41 utc jmettraux :-)
2010-12-03 08:10:08 utc jfding so, we must say many thanks you guys
2010-12-03 08:11:26 utc jmettraux jfding: many thanks for the work on https://github.com/kennethkalmer/ruote-amqp/issues/closed#issue/3
2010-12-03 08:12:26 utc tosch_le jmettraux: after reading the first half of the restful web apps book, i'm unsure if proceeding within the workitems resource of ruote-kit with a '_proceed' param is the right thing to do.
2010-12-03 08:12:49 utc tosch_le somehow, i'd like an own method for that more
2010-12-03 08:13:19 utc jmettraux we are limited to a PUT, aren't we ?
2010-12-03 08:14:09 utc tosch_le we are
2010-12-03 08:14:36 utc jmettraux we're putting a new representation, where the _proceed flag is set
2010-12-03 08:14:56 utc tosch_le yes, but that way it's hard to tell the clients how to proceed
2010-12-03 08:15:12 utc tosch_le the have to know that they have to set the proceed flag
2010-12-03 08:15:19 utc jmettraux true
2010-12-03 08:15:34 utc jmettraux we could use DELETE
2010-12-03 08:15:39 utc tosch_le that out-of-band-information and bad, if i understood the book correctly
2010-12-03 08:15:56 utc jmettraux which comes handy since we really want the workitem to be removed from the worklist
2010-12-03 08:16:03 utc jmettraux and continue in the flow
2010-12-03 08:16:13 utc tosch_le yes, this is exactly what i thought, too
2010-12-03 08:17:05 utc jmettraux maybe we could keep _proceed for backward compatibility and go with DELETE
2010-12-03 08:18:00 utc tosch_le +1
2010-12-03 08:19:31 utc tosch_le ok, i'll do that in the next couple of weeks :-)
2010-12-03 08:19:39 utc tosch_le having fun with etag right now
2010-12-03 08:19:51 utc jmettraux http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html I wonder if it's OK for DELETE to have a body
2010-12-03 08:20:02 utc jmettraux PUT and proceed
2010-12-03 08:21:44 utc tosch_le i suppose a delete may have a body: "A successful response SHOULD be 200 (OK) if the response includes an entity describing the status, 202 (Accepted) if the action has not yet been enacted, or 204 (No Content) if the action has been enacted but the response does not include an entity."
2010-12-03 08:21:50 utc jmettraux looking forward to see your work on ETag
2010-12-03 08:22:10 utc jmettraux response ;-)
2010-12-03 08:22:15 utc jmettraux not request
2010-12-03 08:22:19 utc tosch_le ahhhh
2010-12-03 08:22:28 utc tosch_le sorry.
2010-12-03 08:22:34 utc jmettraux no worries
2010-12-03 08:22:48 utc tosch_le but that's not a problem imho: there are just two requests needed
2010-12-03 08:23:00 utc tosch_le first put, then delete
2010-12-03 08:23:18 utc jmettraux not atomic
2010-12-03 08:23:26 utc tosch_le yes.
2010-12-03 08:23:53 utc tosch_le but it isn't an atomic operation, isn't it? it updates a workitem and moves it forward
2010-12-03 08:24:25 utc jmettraux actually, it removes the workitem from the worklist and proceeds it (replying to the engine)
2010-12-03 08:24:38 utc jmettraux you're are right
2010-12-03 08:24:55 utc jmettraux ruote and its storages are doing the version control for us
2010-12-03 08:25:19 utc jmettraux so we can avoid issues
2010-12-03 08:27:21 utc tosch_le "if modified" and "if not modified" ftw
2010-12-03 08:27:32 utc jmettraux +1
2010-12-03 08:28:47 utc jmettraux the ruote storages already have "revs" that could be used as etags
2010-12-03 08:29:00 utc jmettraux or could be leverages to build etags
2010-12-03 08:29:39 utc tosch_le i use them as etags
2010-12-03 08:29:59 utc jmettraux great ! :-)
2010-12-03 08:30:04 utc tosch_le at least, for single workitems and expressions for now
2010-12-03 08:30:20 utc jmettraux you found the shortcut !
2010-12-03 08:30:34 utc tosch_le we talked about that iirc
2010-12-03 08:30:47 utc jmettraux aaah
2010-12-03 08:30:55 utc jmettraux btw, have you seen the new logo ?
2010-12-03 08:31:00 utc tosch_le so you showed me the shortcut
2010-12-03 08:31:05 utc tosch_le not yet
2010-12-03 08:31:08 utc tosch_le it#
2010-12-03 08:31:17 utc tosch_le it's in ruote-on-rails, isn't it?
2010-12-03 08:31:29 utc jmettraux yes
2010-12-03 08:31:53 utc jmettraux had to drop the -on-rails, we're still looking for a way to integrate it
2010-12-03 10:01:07 utc tosch_le jmettraux: i really like the new logo!
2010-12-03 10:01:13 utc jmettraux :-)
2010-12-03 10:57:34 utc tosch_le the workitems resource should respect if-match headers now when workitems are pushed
2010-12-03 11:00:57 utc jmettraux nice :)
2010-12-03 11:04:30 utc jmettraux merged, many thanks !
2010-12-03 11:05:02 utc tosch_le was not sure if check_if_match_etag is an appropriate method name, but we may change that anytime
2010-12-03 11:05:24 utc jmettraux OK
2010-12-03 11:25:32 utc tosch_le applied the same for the expressions resource
2010-12-03 11:34:22 utc jmettraux merged
2010-12-03 11:34:38 utc jmettraux sorry, I'm busy preparing an exam, having a quick break
2010-12-03 11:35:29 utc tosch_le no worries!
2010-12-03 12:45:41 utc jmettraux back
2010-12-03 12:53:22 utc jmettraux tosch_le: we could do the same with ruote-kit and ruote-on-rails : I could drop my repo and commit to yours
2010-12-03 12:53:25 utc jmettraux wdyt ?
2010-12-03 13:06:13 utc tosch_le i don't mind – both ways are ok for me.
2010-12-03 13:09:04 utc jmettraux I want to point to 1 repository
2010-12-03 13:24:35 utc tosch_le jmettraux: i know. but it's github after all, there will always be forking, the people can handle that. perhaps it's time for http://ruote.rubyforge.org/ruote-kit.html
2010-12-03 13:24:55 utc tosch_le with a 'source' link to my repo there
2010-12-03 13:25:07 utc jmettraux http://ruote.rubyforge.org/source.html
2010-12-03 13:25:37 utc jmettraux give me some time to relook the website
2010-12-03 13:25:45 utc tosch_le that points to kenneth' repo. we could even use that one as we both have write access there
2010-12-03 13:25:54 utc jmettraux do you want a page for ruote-kit ?
2010-12-03 13:26:58 utc tosch_le at the moment: no. in a few months perhaps – i'll have to think about the best content for such a page
2010-12-03 13:27:42 utc jmettraux ok
2010-12-03 13:27:57 utc jmettraux Kenneth is unreachable
2010-12-03 13:28:04 utc jmettraux I prefer to point to your repo
2010-12-03 13:28:26 utc jmettraux well, he is reachable, but he has 0 time for open source
2010-12-03 13:28:46 utc tosch_le after all, it's github – forks are a perfect means for collaboration there and people can handle that imho. let us just point to one repo in all the docs; everything else may be left unchanged.
2010-12-03 13:29:17 utc jmettraux ok
2010-12-03 13:31:40 utc jmettraux http://ruote.rubyforge.org/source.html updated
2010-12-03 13:32:21 utc tosch_le there's a typo in the link github.com/tosche instead of just tosch
2010-12-03 13:33:08 utc jmettraux ouch
2010-12-03 13:33:44 utc jmettraux fixed, thanks !
2010-12-03 13:38:06 utc tosch_le wow: https://build.opensuse.org/package/view_file?file=ruote-kit.spec&package=rubygem-ruote-kit&project=Maemo:MeeGo-Infra&srcmd5=e1b157eb248b8a0f9f0c07f2edcda17b
2010-12-03 13:39:03 utc jmettraux ouch, wrong license
2010-12-03 13:39:35 utc jmettraux lbt: hello, were can we report meego issues ?
2010-12-03 13:40:09 utc jmettraux ruote is MIT
2010-12-03 13:40:20 utc tosch_le the file itself says: "Please submit bugfixes or comments via http://bugs.opensuse.org/"
2010-12-03 13:40:47 utc jmettraux ouch, sounds a lot like /dev/null
2010-12-03 13:42:22 utc tosch_le lol
2010-12-03 13:45:06 utc jmettraux oh well... it's for meego's internal usage... they're not selling it
2010-12-03 13:46:03 utc tosch_le it's very public for 'internal usage'
2010-12-03 13:46:43 utc jmettraux IIRC they need the package because "gem install" is not OK with their admins
2010-12-03 14:48:20 utc lbt jmettraux: it's a bug for sure
2010-12-03 14:48:58 utc lbt it was auto-packaged by the opensuse ruby2rpm script
2010-12-03 14:49:15 utc lbt I will fix this
2010-12-03 14:49:58 utc lbt the answer is bugs.meego.com though ... and this would be a suitable bug to log there (although we're obscure enough that people may be confused)
2010-12-03 15:04:13 utc tosch_le i'll leave now. have a nice weekend!