ejabberd - Comments for "Mnesia schema/XMPP-RPC Generator"

Clarification

James Bowery — Sun, 01 Jan 2006 09:29:19 +0000

When I said "it doesn't start with modeling the data" I was referring to rapid prototyping rather than Rails.

Maybe a slightly different approach is best

James Bowery — Sun, 01 Jan 2006 04:36:47 +0000

Sorry for the delay but we had to discuss more what would be best here and we thought maybe the strategy should be different from what Rails supplies (modeling language drives database schema with scaffold-generated forms). The problem with the Rails approach to rapid prototyping is that it doesn't start with modeling the data -- it starts with workflow specification and forms design. Modeling the data follows from that.

What we have: a bunch of XForms. We can generate associated descriptions such as WSDL, as well as other descriptions of the fields.

What we need: an easy way to generate:

1) A prototype Mnesia store (table) for each XForm to handle just the fields for that XForm. No factoring or communication between XForms is required for the prototype. Refinement of the prototype requires factoring and inter-XForm-communications/dataflow but it can be put off till the prototype looks reasonable.

2) Simple CRUD services for each XForm's store.

We are focused on supporting XMPP via HTTP polling but straight REST-HTTP would suffice since this is a browser based programming.

Is there any model

mfoss — Mon, 05 Dec 2005 08:09:54 +0000

Is there any model specification language for Mnesia/J-EAI that would generate a Mnesia database with XMPP-RPC service interface so we can just hook in our screens to the RPC calls and start entering data?

I don't understand the question. Do you want ejabberd to listen RPC calls and accept commands to: create new database, remove, add elements, remove, search, get...?