Hopbot log for 2008-09-14 - Helma IRC channel: #helma on irc.freenode.net

2008-09-14:

[8:20] <decke> good morning
[9:53] <zumbrunn> good morning decke
[10:07] <decke> has already someone played with nginx in front of jetty/helma ?
[10:08] * zumbrunn never even heard of it
[10:08] <zumbrunn> googling...
[10:09] <zumbrunn> this? http://nginx.net/
[10:09] <decke> yes
[10:09] <decke> like lighttpd - a stupid fast single threaded webserver
[10:09] <zumbrunn> *and* mail proxy!
[10:10] <decke> yeah that's a bit weird...
[10:10] <zumbrunn> that's an interesting combination
[10:11] <zumbrunn> that combination really makes it sound interesting to me
[10:12] <zumbrunn> written in what? C?
[10:12] <decke> jep
[10:12] <decke> and there is a fairly good wiki for it
[10:13] <decke> http://wiki.codemongers.com/Main
[10:13] <decke> the pictures look a bit like the helma woman *g*
[10:13] <zumbrunn> haha
[10:14] <zumbrunn> :-)
[10:15] <decke> i already use it with my mediaservice which i have worked on the last few weeks and it really rocks...
[10:17] <decke> and when i think about jetty and apache and that they are connected with simple http proxying nowadays that sounds like overkill using apache for such simple tasks
[10:18] <zumbrunn> yes, certainly
[10:20] <zumbrunn> on the other hand, the question is whether one needs to have anything in front of jetty
[10:22] <decke> for static content i would prefer to have a fast webserver ...
[10:22] <decke> and for proxying more than one helma instance you would need one too
[10:23] <zumbrunn> yes, unless one would use jetty for that as well
[10:26] <decke> newer jetties use java.nio so that is pretty much like the single threaded webservers with non blocking i/o do
[10:28] <zumbrunn> nginx looks interesting in deed
[10:32] <decke> looks like i have found it... http://wiki.codemongers.com/NginxHttpUpstreamModule
[10:33] <decke> the equivalent to mod_proxy
[18:11] <bard> I'm using built-in functions for user management (registerUser etc), is it possible to associate a model and a uri to user objects so that users would have /myapp/users/joesmith? I'm trying with _children = collection(User) in Root/type.properties with no luck...
[18:14] <decke> users = collection (User)
[18:14] <decke> would do the trick
[18:14] <decke> and users.accessname = USER_NICK
[18:15] <decke> or whatever your column with the username would be
[18:17] <bard> uhm. now urls are generated as /app/5 (instead of /app/joesmith) but accessing the url still yields "object not found". (btw I'm using the embedded db)
[18:18] <bard> "are generated as" -> I mean by user.href()
[18:26] <bard> decke: what url should users = collection (User) generate for a given user?
[18:29] <decke> that depends where you define that...
[18:29] <decke> in Root/type.properties it gets /users/<value>
[18:30] <decke> as long as there is now users.accessname helma uses the ID which is your case
[18:30] <decke> now=no
[18:30] <bard> odd
[18:30] <decke> no that's absolutely fine
[18:31] <bard> I mean, what I'm getting is odd
[18:31] <bard> I have Root/type.properties with just users = collection(User) and nothing else now
[18:31] <bard> user.href() generates (e.g.) /5
[18:31] <decke> yeah as expected
[18:32] <bard> uhm, I thought you said it should generate /users/5
[18:32] <decke> oh yeah... you should reload the app you had _children before
[18:33] <bard> I've just deleted the db, restarted the app and added a user, same behaviour...
[18:34] <bard> and loading /5 or /users/5 still results in 'object not found'...
[18:35] <decke> anything in the logfile?
[18:36] <bard> yep, not very helpful I'm afraid: [2008/09/14 21:39:31] [ERROR] null: helma.framework.NotFoundException: Object not found.
[18:37] <decke> and events.log?
[18:37] <decke> helma.<yourapp>.event.log
[18:38] <bard> I don't have either, probably because I have logDir = console
[18:38] <decke> it's getting tricky then
[19:05] <bard^> ok, so the problem seems to be that you cannot do that with users
[19:05] <bard^> just tried with an ordinary object and it works fine
[19:05] <bard^> i.e. with an ordinary descendant of HopObject, created via new Foo() and added to root via root.foos.add(foo)
[19:06] <decke> you definitely can - otherwise http://www.club3k.at/np/decke would not work...
[19:07] <bard^> maybe part of the problem is that helma creates a HopObject named "users" with id=1 automatically?
[19:07] <bard^> and that overrides the collection set in Root/type.properties...
[19:08] <bard^> maybe this is specific to the embedded db, I don't know. but I set up things the same with User and Foo, and Foo works, while User doesn't.
[19:08] <decke> i never worked with the embedded db just mysql
[19:10] <bard^> are you using app.registerUser and friends too?
[19:11] <decke> no just root.add(user)
[19:12] <decke> we used app.registerUser in the past - but that gave us a lot of problems
[19:12] <decke> but that app is helma 1.4 specific anyway
[19:15] <bard^> well, then it still seems you can't publish user objects if you use registerUser etc. I guess I'll do my own user management too.

 

 

In the channel now:

Logs by date: