Hopbot log for 2007-12-15 - Helma IRC channel: #helma on irc.freenode.net

2007-12-15:

[9:34] <zumbrunn> philmaker, are you awake?
[9:34] <philmaker> hi yes for short bit
[9:35] <zumbrunn> I'm just thinking about what exactly would be needed for the ajax data store you've been talking about
[9:35] <philmaker> good morning
[9:35] <zumbrunn> I'm still not exactly sure about the functionality you are after
[9:35] <philmaker> I understand
[9:35] <zumbrunn> and what you would need that helma can't currently give you out of the box
[9:36] <zumbrunn> thinking...
[9:37] <zumbrunn> you would receive a json string from the client, right?
[9:37] <zumbrunn> you could set a hopobject's property to that json string
[9:37] <philmaker> right - I don't think that JSON communicated data really would need to be stored in a JSON format precisely
[9:37] <zumbrunn> and the built-in db will persist it just fine
[9:38] <philmaker> Maybe I should look at how CouchDB stores their data
[9:38] <philmaker> re: and the built-in db will persist it just fine
[9:38] <philmaker> that was my original intent
[9:39] <philmaker> yes: receive a json string from the client,
[9:39] <zumbrunn> I mean, if persisting chunks of json is what you are after, json is just a string
[9:39] <zumbrunn> which means you don't even have to do anything with it on the helma side
[9:40] <zumbrunn> no, json specific woodoo
[9:40] <zumbrunn> without the comma
[9:40] <zumbrunn> no json specific woodoo
[9:41] <zumbrunn> you just want to store the string and then return that string when the time is right
[9:41] <zumbrunn> what am I missing?
[9:47] <philmaker> be able to use JSONPath via rest and the url
[9:48] * zumbrunn goes looking at jsonpath again...
[9:49] <philmaker> Very similar to that project I mailed you about. But I don't want to discuss that project on IRC really.
[9:50] <philmaker> be able to extract/return only subnodes of a given JSON tree
[9:51] <zumbrunn> only the subnode aspect?
[9:51] <zumbrunn> or the full feature set of jsonpath?
[9:51] <philmaker> no
[9:51] <zumbrunn> either way...
[9:51] <philmaker> right
[9:51] <zumbrunn> you could still store the json strings as hopobject properties
[9:52] <zumbrunn> and then use jsonpath to query on the helma server-side
[9:53] <philmaker> and then each HopObject would be the root of a JSON string...
[9:54] <zumbrunn> yes, or of several
[9:54] <zumbrunn> depending on how you set up the url structure and access rights
[9:55] <philmaker> I'll consider playing more with this and Helma
[9:55] <zumbrunn> I mean, you would want to use jsonpath on specifc chunks of json you stored, right?
[9:55] <zumbrunn> not on entire collections of json strings
[9:55] <philmaker> I just think it would be cool to use Helma for it's normal intended use - plus as a database for JSON
[9:56] <philmaker> re: not on entire collections of json strings
[9:56] <philmaker> not really sure which way to go
[9:57] <philmaker> I could start with the former
[9:57] <philmaker> I'm retiring shortly...
[10:00] <zumbrunn> does jsonpath work on parsed json, meaning the resulting javascript object or on the json string?
[10:01] <philmaker> not sure
[10:01] <philmaker> on the resulting javascript object would be helpful
[10:02] <zumbrunn> if it's the resulting object, then it would be really easy to just merge the different items of a collection into a parent object, for example
[10:03] <zumbrunn> (and then use jsonpath on that)
[10:20] <philmaker> Do you know whether Helma supports the servlet filter mechanism? I would be nice to have but the not found page might work as well.
[10:25] <zumbrunn> that would probably be a jetty config, right?
[10:25] <zumbrunn> don't know

 

 

In the channel now:

Logs by date: