fluid-work IRC Logs-2009-12-01

[02:54:35 EST(-0500)] * boyan1 (n=boyan@62.44.108.2) has joined #fluid-work
[04:49:33 EST(-0500)] * joan2 (n=jgarci@120.Red-213-96-26.staticIP.rima-tde.net) has joined #fluid-work
[04:50:08 EST(-0500)] <joan2>
[04:51:02 EST(-0500)] <joan2> hi. I've got couchdb and lucene and view working ... at least, as a proof of concept.
[06:18:32 EST(-0500)] * sveto_ (n=sveto@85.187.19.183) has joined #fluid-work
[06:43:43 EST(-0500)] <joan2> hi sveto. I have it working ... both, queries using views and queries using lucene.
[06:43:54 EST(-0500)] <joan2> sveto: and also delete.
[06:49:13 EST(-0500)] <sveto_> joan2: that's great, I tested a bit yesterday but got an error saying "Access to restricted URI denied" which is pretty strange. I'll have a look a database.js now.
[06:49:16 EST(-0500)] <joan2> sveto: I commit the proof-of-concept in scrachpad/bug-parade (database [html/js]). It is a draft but seems to work pretty well.
[06:49:57 EST(-0500)] <joan2> sveto: you need an Apache2 to ProxyPassReverse to the same domain.
[06:53:03 EST(-0500)] <joan2> sveto: in fact I execute my component through the same apache (http://localhost/bug-parade/html/database.html) and I reverse proxy /couchdb/ - to - "http://localhost:5984/" where couchdb lives.
[06:53:39 EST(-0500)] <sveto_> joan2: I'm not familiar with this directive... How do I do a setup?
[06:54:30 EST(-0500)] <joan2> sveto: this works for me. I suppose, my database component has to be a future subcomponent of artifact-comments (kettle server-side).
[06:56:03 EST(-0500)] <joan2> sveto: try search for: "apache2 ProxyPassReverse howto". you'll find plenty of documentation.
[06:59:02 EST(-0500)] <sveto_> joan2: ok, is this a problem with ajax?
[07:01:01 EST(-0500)] <boyan1> sveto_: the "Access to restricted URI denied" error is due to the same origin policy for ajax
[07:01:13 EST(-0500)] <joan2> I don't think so. It's a safetyness restriction. As far as I know, you can only ajax services from the same domain where you loaded the page (referer).
[07:02:06 EST(-0500)] <joan2> boyan: thanks.
[07:06:03 EST(-0500)] <boyan1> you might get that error when you test something locally that works well on the server
[07:06:18 EST(-0500)] <boyan1> this is because of the browser enforcing that same origin policy
[07:06:45 EST(-0500)] <boyan1> you can override that setting (in firefox) by typing about:config and setting security.fileuri.strict_origin_policy to false
[07:06:59 EST(-0500)] <boyan1> this should make it work
[07:07:35 EST(-0500)] <boyan1> although in theory it is not safe because a site might execute malicious code coming from another site
[07:09:16 EST(-0500)] <boyan1> sveto_, joan2: not sure if this is the problem with you, but you can give it a try (read above)
[07:11:58 EST(-0500)] <sveto_> boyan1: I tried that, and it didn't help... moreover I'm a bit confused as yesterday I ran my web server locally, my db server locally and made a call from my machine and still got that error... maybe I've overlooked some call
[07:14:06 EST(-0500)] <boyan1> sveto_: hmm, then the problem is somewhere else, no more ideas where
[07:16:00 EST(-0500)] <joan2> sveto: I think that same origin policy also check the port (and the [address / domain] too). But I'm not 100% sure
[07:25:45 EST(-0500)] <boyan1> joan2, sveto: yes, it does check the port
[07:38:20 EST(-0500)] <sveto_> boayn1: so that was the problem
[07:46:05 EST(-0500)] * boyan1 (n=boyan@62.44.108.2) has left #fluid-work
[08:11:40 EST(-0500)] * Justin_o (n=Justin@142.150.154.171) has joined #fluid-work
[08:18:56 EST(-0500)] * athena (n=athena@adsl-75-58-127-15.dsl.wlfrct.sbcglobal.net) has joined #fluid-work
[08:25:02 EST(-0500)] * laurel (n=Laurel@142.150.154.178) has joined #fluid-work
[08:35:19 EST(-0500)] * jessm (n=Jess@c-71-232-1-65.hsd1.ma.comcast.net) has joined #fluid-work
[08:38:29 EST(-0500)] * joan2 (n=jgarci@120.Red-213-96-26.staticIP.rima-tde.net) has joined #fluid-work
[09:07:08 EST(-0500)] * fj4000 (n=Main@CPE0018f85ab63e-CM001692f5798c.cpe.net.cable.rogers.com) has joined #fluid-work
[09:13:39 EST(-0500)] * michelled (n=michelle@142.150.154.193) has joined #fluid-work
[09:44:58 EST(-0500)] * clown (n=clown@142.150.154.101) has joined #fluid-work
[09:46:00 EST(-0500)] * colinclark (n=colin@bas2-toronto09-1176131079.dsl.bell.ca) has joined #fluid-work
[09:47:07 EST(-0500)] * clown (n=clown@142.150.154.101) has left #fluid-work
[09:54:16 EST(-0500)] * yura (n=yura@142.150.154.132) has joined #fluid-work
[10:20:27 EST(-0500)] <jamon> laurel: blog was copied, http://142.150.154.58/blog/wp-login.php
[10:20:37 EST(-0500)] * colinclark (n=colin@142.150.154.101) has joined #fluid-work
[10:26:28 EST(-0500)] <laurel> jamon: thanks thanks
[10:34:20 EST(-0500)] * anastasiac (n=team@142.150.154.189) has joined #fluid-work
[10:54:54 EST(-0500)] * EricDalquist (n=dalquist@bohemia.doit.wisc.edu) has joined #fluid-work
[10:55:32 EST(-0500)] * colinclark (n=colin@142.150.154.101) has joined #fluid-work
[11:12:28 EST(-0500)] * elicochran (n=elicochr@adsl-70-137-161-118.dsl.snfc21.sbcglobal.net) has joined #fluid-work
[11:19:00 EST(-0500)] * mackrauss (n=Armin@user147-236.wireless.utoronto.ca) has joined #fluid-work
[11:54:19 EST(-0500)] * Justin_o (n=Justin@142.150.154.171) has joined #fluid-work
[12:21:07 EST(-0500)] * clown_afk (n=clown@142.150.154.101) has joined #fluid-work
[12:29:12 EST(-0500)] <joan2> colin ?
[12:29:27 EST(-0500)] <Justin_o> joan2: he is in a meeting at the moment
[12:29:39 EST(-0500)] <joan2> no problem.
[12:31:00 EST(-0500)] <joan2> justin: I created the database component that we talked about. As a couchdb wrapper
[12:31:38 EST(-0500)] <joan2> justin: my idea is using it inside kettle or server stuff.
[12:32:19 EST(-0500)] <joan2> justin: for store/retrieve the artifact comments, what do you think about it?
[12:33:45 EST(-0500)] <Justin_o> joan2: hmm... not to sure... didn't get a chance to look at your code yet. Sorry. But colin should be back in a minute or two
[12:34:12 EST(-0500)] <joan2> ok.
[12:39:52 EST(-0500)] <colinclark> joan2: I haven't had a lot of time to look at your work so far.
[12:40:03 EST(-0500)] <colinclark> It's something I'm going to get some time to do today and tomorrow.
[12:40:14 EST(-0500)] <colinclark> I think there are some larger architectural concerns to think through
[12:40:51 EST(-0500)] <joan2> colin: Yes.
[12:41:16 EST(-0500)] <colinclark> You done a nice job of creating a low-level API for building up Couch URLs and making various RESTful requests, but I feel like there are some issues we're missing here. And regrettably I haven't yet had a time to fully think through them.
[12:41:28 EST(-0500)] <colinclark> Superficially, I see a couple of issues with the code you've got now.
[12:41:43 EST(-0500)] <colinclark> 1. You're constructing it as a View, yet I can't imagine it really has any view-related concerns.
[12:42:13 EST(-0500)] <colinclark> Since you've got things like empty events and selectors blocks, it's clear that this isn't a proper View at all.
[12:42:21 EST(-0500)] <colinclark> So you needn't use fluid.initView()
[12:42:40 EST(-0500)] <colinclark> But the absence of events speaks to one of the larger issues I'd like to think through a bit more...
[12:42:49 EST(-0500)] <colinclark> And that's the issue of synchronicity.
[12:43:11 EST(-0500)] <colinclark> Your code is written to be used only in a synchronous context, which is interesting.
[12:43:12 EST(-0500)] <joan2> colin: the code its only early fluid subcomponent.
[12:43:28 EST(-0500)] <colinclark> joan2: Cool. That's totally understandable.
[12:43:55 EST(-0500)] <colinclark> I hope I don't sound like I'm criticizing, this is just advice and thoughts off the top of my head.
[12:44:05 EST(-0500)] <joan2> colin: this code has to run in server side, so you need synchronous behaviour like "a kind of transaction"
[12:44:19 EST(-0500)] <colinclark> joan2: Sure, I realize that.
[12:44:51 EST(-0500)] <colinclark> But there's a larger pattern here: it's not uncommon for our code-at different levels and running in different locations-to need to read data from a feed.
[12:44:52 EST(-0500)] <joan2> colin: the need to post the early code is that i didn't found such database object in kettle (only browse part)
[12:45:25 EST(-0500)] <colinclark> And so, in part, I want to start thinking about what some of the bigger-picture issues around data access look
[12:45:40 EST(-0500)] <colinclark> and try to design APIs that are general enough to be reused in different contexts and both on the client and server sides.
[12:45:41 EST(-0500)] <joan2> colin: I tryed to cover all the basic need (browse, pageable query, full-text lucene pageable query, insert, update, delete)
[12:46:15 EST(-0500)] <colinclark> Yep, I think you've done a good job of covering the essentials of access to Couch
[12:47:28 EST(-0500)] <colinclark> joan2: There's one next step before I'd suggest you start using it in the comments work...
[12:47:30 EST(-0500)] <colinclark> Unit tests.
[12:48:02 EST(-0500)] <colinclark> I think if you can write some unit tests to ensure that the code is working reasonable, we'll be in good shape.
[12:48:18 EST(-0500)] <joan2> colin: the database.html is a fast unit test. I'll write the unit test as has to be done.
[12:48:28 EST(-0500)] <colinclark> joan2: Awesome, thanks
[12:49:03 EST(-0500)] <colinclark> So I'll continue to puzzle through some of the bigger issues about data access, and it's something we can start to chat more about on the list over the next few days.
[12:49:10 EST(-0500)] <colinclark> Seem reasonable, joan2?
[12:50:28 EST(-0500)] <joan2> yes.
[12:50:50 EST(-0500)] <colinclark> Great. Nice work.
[12:54:59 EST(-0500)] <joan2> colin: couchdb seems a good database. Did you already tested it with hundreds of thousands of documents?
[12:55:42 EST(-0500)] <colinclark> joan2: We've done some larger-scale tests. yura could probably fill you in on some of the details, since he was involved in that work.
[12:55:51 EST(-0500)] <colinclark> But I agree, I think it's a pretty good database, yes.
[12:55:59 EST(-0500)] * jhung_ca (n=Jon@H204.C204.cci.switchworks.net) has joined #fluid-work
[13:00:41 EST(-0500)] * justin_o (n=jmo@user145-63.wireless.utoronto.ca) has joined #fluid-work
[13:02:40 EST(-0500)] <joan2> colin: Tomorrow more. Unit testing and placing the code in a proper place (I reused parade space to speed up the API write and test).
[13:02:57 EST(-0500)] <joan2> bye.
[13:23:09 EST(-0500)] * justin_o_ (n=jmo@142.150.154.101) has joined #fluid-work
[13:27:10 EST(-0500)] * justin_o_ (n=jmo@142.150.154.101) has joined #fluid-work
[13:27:35 EST(-0500)] * justin_o__ (n=jmo@142.150.154.101) has joined #fluid-work
[13:30:12 EST(-0500)] * Justin_o_ (n=Justin@142.150.154.171) has joined #fluid-work
[13:31:01 EST(-0500)] * mackrauss (n=Armin@142.150.154.101) has joined #fluid-work
[14:51:06 EST(-0500)] * Justin_o (n=Justin@142.150.154.171) has joined #fluid-work
[15:00:14 EST(-0500)] * laurel (n=Laurel@142.150.154.178) has left #fluid-work
[15:43:24 EST(-0500)] * clown_afk (n=clown@142.150.154.101) has joined #fluid-work
[15:55:27 EST(-0500)] * Justin_o (n=Justin@142.150.154.171) has joined #fluid-work
[16:39:47 EST(-0500)] * sgithens342f (n=sgithens@149-166-143-223.dhcp-in.iupui.edu) has joined #fluid-work
[17:12:22 EST(-0500)] * clown_afk (n=clown@142.150.154.101) has left #fluid-work
[17:13:28 EST(-0500)] * clown (n=clown@142.150.154.101) has joined #fluid-work
[17:14:23 EST(-0500)] * clown (n=clown@142.150.154.101) has left #fluid-work
[17:18:06 EST(-0500)] * anastasiac (n=team@142.150.154.189) has left #fluid-work
[18:11:31 EST(-0500)] * yura (n=yura@user187-223.wireless.utoronto.ca) has joined #fluid-work