[Moonbeam-users] moonbeam next steps

[hlan <he...@hl...>]

hi mathew,

i am glad that you going to give it a try.
for me it's important, cause users are going to dig deeper
into the bugs, and help me define the next level of requirements.

well, regarding your questions:

1. license change
actually i tended to release it under bsd style license and then 
switched to gpl, because i was hoping to find co-developers more easily.

the way the server is build, which means seperated into moonbeam-core,
and the app (new term "engine") which sits atop of the core and holds the 
application logic, should offer the possibility to run it dual licensed.

take it as a kind of lgpl scenario, whereas your development efforts
regarding the instant messenger dont need to be opened to the public,
but addon's and changes to the moonbeam-core do.

i think this would be the best solution for both sides.
does your project allow such a scenario?
  
2. short term goals

- new message format
the default message format is going to be replaced.
we found a new data format (taken from the jabber poeple)
which seems to fit our needs just perfectly. it's pretty 
flexible and still not to complex.

- core layout
the moonbeam core is currently party rewritten,
trying to get a clear role seperation between te main components:

	a, connection mananger
	b, client connection
	c, environment
	d, engine
	e, services 
	
- message flow
the message flow is changed from the initial idea,
which was based on a processor chain, to a scenario where any
message gets delivered to the engine, which then decides on it.

futhermore i am currently thinking about integration
of message filters and processor chains at the engine level.

- event handling
event handling between the core components is introduced
ans implemented.

2.1 a parallel task would be to define common requirements.
taking a working core and  a clear component layout, it would
be time to decided on the default behaviour and features (aka services)
which should be common to the any engine (i.e. authorisation).

this is a part where i would e glad to get input from your side,
so taht we can decide on core-services and requirements for your own app.
best thing would be to co-develop these core-services, therefore the
license proposal above.

these are the short term goals.
i think the interesting part is the definition of common services
and there definition.

so long, heiko


-- 
 --_ __ -     ___ _ . -- __      -