/razpub/README.txt

 1This code is copyrighted by Razvan Cojocaru and presently shared under the Apache license...see LICENSE.txt
 2
 3What's this?
 4------------
 5Lots of under-piping code that I wish I didn't have to write but needed to. 
 6
 7Why?
 8----
 9Well, just like i wish I didn't have to write it, there's no point in making others write it, 
10should they need it. It's not like it's anything smart so far and possibly not useful, but 
11maybe others find it useful. The more the better.
12
13
14Details
15-------
16See com.razie.pub's package-info.java and the others, for up-to-date details. Here's an abstract.
17
18The aim is to support a grid/fabric like framework for smart assets. Read-on to figure out the pieces of the puzzle :)
19
20There's a very simple and light and especially embedded http server.
21
22On top of this there's a simple LightSoa framework, which allows you to easily create "services": 
23just have a Java class, annotate the methods you want available over http and register it with the server.
24While the servlet thing is great, it's not that easy to use and most services/methods are really simple 
25and this way you can test them either directly by Java calls or via the http server.
26
27Assets - bastardized word, but here it is. You can think of them as ManagedEntities (see OSS/J) or something 
28like stateful beans. Just like services are simple classes (one instance to serve all), the assets are 
29individual objects which you can access remotely. They however have state and could be persisted.
30They are developed much like the services (annotated methods).
31
32There's some very basic multi-threading support (life), which keeps track of the threads and what they're doing.
33I envision some beings jumping up and down inside the program, which need to breathe(). There's also workers which 
34only process() something.
35
36Two things I'm investigating are drawing and streaming.
37
38Drawing - basically any code anywhere will draw something. Even if it doesn't, the objects it uses could be seen by 
39someone somewhere, be it a web page, AJAX, SVG, Eclipse, SWING ... god knows what. So, here's a simple and 
40generic drawing framework. 
41
42Streaming - instead of hard-coding the communication protocols throughout the code, I'm trying to abstract the basics
43of a communications framework.
44
45
46Roadmap
47-------
48I will only maintain this as I need to. If there's some large user community developing (doubt that, really), 
49we'll see - I could co-op some volunteers.
50
51I will add more code as I need it/write it for all kinds of reasons.
52