jsgui3-server 0.0.121 → 0.0.123

package/resources/compile/server-resource-compilation.js

@@ -1,43 +1,43 @@
-// Or will use some different 'Bundler' classes for the moment.
-// Bundlers will extract CSS from JS too.
-
-// Will make use of features already in jsgui to handle / do compilation.
-
-
-// Want compilation to be handled lower level within the jsgui system.
-//  jsgui.compile(code, compilation_options);
-
-// jsgui compiler toolkit could go in lang-tools or even lang-mini.
-//  there is also the jsx compiler, should be similar to call to Babel.
-
-
-// Handling rust => wasm compilation will be nice too.
-// And other languages that compile to WASM, such as C and C++.
-
-// Much of it will require HD space.
-//  Want to wrap that in a convenient interface that could be upgraded to RAM drive,
-//   network RAM drive etc.
-
-// May need to install / verify installation of necessary compilers, eg cargo, gcc.
-
-// And specific compilation / compiler resources?
-//  As resources, the management of their access will be controlled (maybe made available remotely) programatically.
-
-// Want babel, esbuild
-// Also rust.
-// Rust to integrated WASM would be very nice.
-//  Being able to write rust files that seamlessly connect with JS files.
-//   Or even integrating Rust code within a js file....
-//    or xjs?
-
-
-
-
-
-
-
-
-
-
-
-
+// Or will use some different 'Bundler' classes for the moment.
+// Bundlers will extract CSS from JS too.
+
+// Will make use of features already in jsgui to handle / do compilation.
+
+
+// Want compilation to be handled lower level within the jsgui system.
+//  jsgui.compile(code, compilation_options);
+
+// jsgui compiler toolkit could go in lang-tools or even lang-mini.
+//  there is also the jsx compiler, should be similar to call to Babel.
+
+
+// Handling rust => wasm compilation will be nice too.
+// And other languages that compile to WASM, such as C and C++.
+
+// Much of it will require HD space.
+//  Want to wrap that in a convenient interface that could be upgraded to RAM drive,
+//   network RAM drive etc.
+
+// May need to install / verify installation of necessary compilers, eg cargo, gcc.
+
+// And specific compilation / compiler resources?
+//  As resources, the management of their access will be controlled (maybe made available remotely) programatically.
+
+// Want babel, esbuild
+// Also rust.
+// Rust to integrated WASM would be very nice.
+//  Being able to write rust files that seamlessly connect with JS files.
+//   Or even integrating Rust code within a js file....
+//    or xjs?
+
+
+
+
+
+
+
+
+
+
+
+

package/resources/data-resource.js

@@ -1,119 +1,119 @@
-// Change name to HTTP_Resource?
-
-// May be worth doing more on local / remote transformation resources.
-//  Even loading the remote code to run locally where applicable.
-
-
-// HTTP_Resource seems like a better name as it processes an HTTP request.
-
-
-var path = require('path'),
-    fs = require('fs'),
-    url = require('url'),
-    jsgui = require('jsgui3-html'),
-    os = require('os'),
-    http = require('http'),
-    libUrl = require('url'),
-    Resource = jsgui.Resource,
-    Cookies = require('cookies'),
-    fs2 = require('../fs2');
-
-
-
-var stringify = jsgui.stringify,
-    each = jsgui.each,
-    arrayify = jsgui.arrayify,
-    tof = jsgui.tof;
-var filter_map_by_regex = jsgui.filter_map_by_regex;
-var Class = jsgui.Class,
-    Data_Object = jsgui.Data_Object,
-    Enhanced_Data_Object = jsgui.Enhanced_Data_Object;
-var fp = jsgui.fp,
-    is_defined = jsgui.is_defined;
-var Collection = jsgui.Collection;
-
-// Extends AutoStart_Resource?
-
-// May need to change around a fair few references to make it workable.
-// May need some more complicated logic to change it to the path for service.
-
-// Possibly Data_Resource could provide images which go alongside the data.
-//  Icons to represent data.
-//  Could make use of the image resource in order to do this.
-//   An image resource could use / be a data resource that provides access to images.
-
-// Ideally want it like image keys, then options for max size and also quality.
-//  
-
-// Data_HTTP_Resource ?
-
-// Handled with request+response.
-//  What about data that needs to be in page load?
-
-// Maybe assume resources always deal with data?
-
-class Data_Resource extends Resource {
-
-    constructor(spec) {
-        super(spec);
-        //this.meta.set('custom_paths', new Data_Object({}));
-        this.custom_paths = new Data_Object({});
-        this.data = {};
-        // want to be able to set specific pieces of data to be available.
-        //  This won't be a full DB API, but a starting point for the client-side app to communicate with the server.
-        //  It will interact with a data model through this.
-    }
-    'start'(callback) {
-        callback(null, true);
-    }
-    'process'(req, res) {
-        console.log('Data_Resource processing HTTP request');
-        var remoteAddress = req.connection.remoteAddress;
-        var custom_paths = this.custom_paths;
-        var rurl = req.url;
-        var pool = this.pool;
-        // should have a bunch of resources from the pool.
-
-        //var pool_resources = pool.resources();
-        //console.log('pool_resources ' + stringify(pool_resources));
-        var url_parts = url.parse(req.url, true);
-        //console.log('url_parts ' + stringify(url_parts));
-        var splitPath = url_parts.path.substr(1).split('/');
-        //console.log('resource site data splitPath ' + stringify(splitPath));
-        if (rurl.substr(0, 1) == '/') rurl = rurl.substr(1);
-        rurl = rurl.replace(/\./g, '☺');
-        //console.log('rurl ' + rurl);
-
-        if (splitPath.length === 2) {
-            if (splitPath[0] === 'data') {
-                let key = splitPath[1], value = this.data[key], t_val = tof(value);
-                //console.log('t_val', t_val);
-                // Other types of data?
-                if (t_val === 'buffer') {
-                    // Encode it as hex / baase64?
-
-                    // Client was expecting text I think.
-                    //  We'll get the data to the client, and have a relatively easy way of making server-side data available to the client.
-
-                    // probably best to send back binary data?
-
-                    var mime_type = 'application/octet-stream';
-                    //console.log('mime_type ' + mime_type);
-                    res.writeHead(200, {
-                        'Content-Type': mime_type
-                    });
-                    res.end(value);
-                }
-            }
-        }
-        // Could consult a map of values to send back.
-        //  A prefixed map would be fine for some applications.
-    }
-}
-
-
-//return Site_CSS;
-
-
-//});
+// Change name to HTTP_Resource?
+
+// May be worth doing more on local / remote transformation resources.
+//  Even loading the remote code to run locally where applicable.
+
+
+// HTTP_Resource seems like a better name as it processes an HTTP request.
+
+
+var path = require('path'),
+    fs = require('fs'),
+    url = require('url'),
+    jsgui = require('jsgui3-html'),
+    os = require('os'),
+    http = require('http'),
+    libUrl = require('url'),
+    Resource = jsgui.Resource,
+    Cookies = require('cookies'),
+    fs2 = require('../fs2');
+
+
+
+var stringify = jsgui.stringify,
+    each = jsgui.each,
+    arrayify = jsgui.arrayify,
+    tof = jsgui.tof;
+var filter_map_by_regex = jsgui.filter_map_by_regex;
+var Class = jsgui.Class,
+    Data_Object = jsgui.Data_Object,
+    Enhanced_Data_Object = jsgui.Enhanced_Data_Object;
+var fp = jsgui.fp,
+    is_defined = jsgui.is_defined;
+var Collection = jsgui.Collection;
+
+// Extends AutoStart_Resource?
+
+// May need to change around a fair few references to make it workable.
+// May need some more complicated logic to change it to the path for service.
+
+// Possibly Data_Resource could provide images which go alongside the data.
+//  Icons to represent data.
+//  Could make use of the image resource in order to do this.
+//   An image resource could use / be a data resource that provides access to images.
+
+// Ideally want it like image keys, then options for max size and also quality.
+//  
+
+// Data_HTTP_Resource ?
+
+// Handled with request+response.
+//  What about data that needs to be in page load?
+
+// Maybe assume resources always deal with data?
+
+class Data_Resource extends Resource {
+
+    constructor(spec) {
+        super(spec);
+        //this.meta.set('custom_paths', new Data_Object({}));
+        this.custom_paths = new Data_Object({});
+        this.data = {};
+        // want to be able to set specific pieces of data to be available.
+        //  This won't be a full DB API, but a starting point for the client-side app to communicate with the server.
+        //  It will interact with a data model through this.
+    }
+    'start'(callback) {
+        callback(null, true);
+    }
+    'process'(req, res) {
+        console.log('Data_Resource processing HTTP request');
+        var remoteAddress = req.connection.remoteAddress;
+        var custom_paths = this.custom_paths;
+        var rurl = req.url;
+        var pool = this.pool;
+        // should have a bunch of resources from the pool.
+
+        //var pool_resources = pool.resources();
+        //console.log('pool_resources ' + stringify(pool_resources));
+        var url_parts = url.parse(req.url, true);
+        //console.log('url_parts ' + stringify(url_parts));
+        var splitPath = url_parts.path.substr(1).split('/');
+        //console.log('resource site data splitPath ' + stringify(splitPath));
+        if (rurl.substr(0, 1) == '/') rurl = rurl.substr(1);
+        rurl = rurl.replace(/\./g, '☺');
+        //console.log('rurl ' + rurl);
+
+        if (splitPath.length === 2) {
+            if (splitPath[0] === 'data') {
+                let key = splitPath[1], value = this.data[key], t_val = tof(value);
+                //console.log('t_val', t_val);
+                // Other types of data?
+                if (t_val === 'buffer') {
+                    // Encode it as hex / baase64?
+
+                    // Client was expecting text I think.
+                    //  We'll get the data to the client, and have a relatively easy way of making server-side data available to the client.
+
+                    // probably best to send back binary data?
+
+                    var mime_type = 'application/octet-stream';
+                    //console.log('mime_type ' + mime_type);
+                    res.writeHead(200, {
+                        'Content-Type': mime_type
+                    });
+                    res.end(value);
+                }
+            }
+        }
+        // Could consult a map of values to send back.
+        //  A prefixed map would be fine for some applications.
+    }
+}
+
+
+//return Site_CSS;
+
+
+//});
 module.exports = Data_Resource;

package/resources/fs-resource.js

@@ -1,147 +1,147 @@
-/*
- if (typeof define !== 'function') {
- var define = require('amdefine')(module);
- }
-
- define(['module', 'path', 'fs', 'url', '../../web/jsgui-html', 'os', 'http', 'url', './resource',
- '../../web/jsgui-je-suis-xml', 'cookies', '../../fs/jsgui-node-fs2-core'],
-
- function(module, path, fs, url, jsgui, os, http, libUrl,
- Resource, JeSuisXML, Cookies, fs2) {
- */
-
-// A RAM FS may be of use here too. Cross-platform, simple to use.
-
-var libpath = require('path'),
-    fs = require('fs'),
-    url = require('url'),
-    //jsgui = require('jsgui3-html'),
-    os = require('os'),
-    http = require('http'),
-    libUrl = require('url'),
-    jsgui = require('jsgui3-html')
-    Resource = jsgui.Resource,
-    Cookies = require('cookies'),
-    fs2 = require('../fs2');
-
-    /*
-
-var stringify = jsgui.stringify,
-    each = jsgui.each,
-    arrayify = jsgui.arrayify,
-    tof = jsgui.tof;
-var filter_map_by_regex = jsgui.filter_map_by_regex;
-var Class = jsgui.Class,
-    Data_Object = jsgui.Data_Object,
-    Enhanced_Data_Object = jsgui.Enhanced_Data_Object;
-var fp = jsgui.fp,
-    is_defined = jsgui.is_defined;
-var Collection = jsgui.Collection;
-*/
-// Extends AutoStart_Resource?
-
-// May need to change around a fair few references to make it workable.
-// May need some more complicated logic to change it to the path for service.
-
-const fnl = require('fnl');
-const obs_or_cb = fnl.obs_or_cb;
-
-const fnlfs = require('fnlfs');
-
-// Cloud_FS_Resource
-// SFTP_FS_Resource
-
-// Publishing an FS resource would enable a directory browsing app.
-//  File_Tree, and connect to the client-side Data_Resource.
-
-const {
-    is_directory, dir_contents
-} = fnlfs;
-
-// This Resource looks to be in a RESTful paradigm. Consider how it would work with GraphQL.
-
-class FS_Resource extends Resource {
-
-    constructor(spec) {
-        super(spec);
-        //this.meta.set('custom_paths', new Data_Object({}));
-        //this.custom_paths = new Data_Object({});
-
-
-        //this.data = {};
-
-        // want to be able to set specific pieces of data to be available.
-        //  This won't be a full DB API, but a starting point for the client-side app to communicate with the server.
-        //  It will interact with a data model through this.
-
-
-        // Could have different types of caching modes too.
-        //  Using fnlfs would be useful too.
-        //  mmfs as a pluggable substitute
-
-        // fnlfs-pro
-
-        this.root_path = spec.root_path || spec.root;
-
-        // can't go below the root path.
-        //  Disallow .. in the given paths.
-
-
-    }
-    // need to promisify this.
-    'start' (callback) {
-        if (callback) {
-            callback(null, true);
-        } else {
-            return true;
-        }
-        
-    }
-
-    'get' (path, callback) {
-        return obs_or_cb((next, complete, error) => {
-
-            (async() => {
-                if (await is_directory(path)) {
-
-                    let full_path = libpath.join(this.root_path, path);
-                    console.log('full_path', full_path);
-
-                    let contents = await dir_contents(full_path);
-                    // however, those are File objects.
-
-                    // try just stringifying them now.
-                    //  No need to handle stringifying here.
-                    complete(contents);
-                } else {
-                    // It's a file.
-                }
-            })();
-        });
-
-        // path is a directory, then return a list of the files there (maybe with metadata)
-        //  nice if we can optionally turn on mmfs but not include it in jsgui itself because it requires ffmpeg / ffprobe.
-        // Could upgrade the FS resource's fs lib.
-        // dir or file
-        // is_directory(path)
-
-        // If it's a file, then it would return a read stream.
-
-
-    }
-    'set' (path, value, callback) {
-        // Overwrite files
-    }
-
-    // Delete
-
-
-
-    /*
-        Does not process HTTP requests itself. Has a Resource_Publisher which contains / refers to this and does the publishing.
-    */
-
-    
-}
-
+/*
+ if (typeof define !== 'function') {
+ var define = require('amdefine')(module);
+ }
+
+ define(['module', 'path', 'fs', 'url', '../../web/jsgui-html', 'os', 'http', 'url', './resource',
+ '../../web/jsgui-je-suis-xml', 'cookies', '../../fs/jsgui-node-fs2-core'],
+
+ function(module, path, fs, url, jsgui, os, http, libUrl,
+ Resource, JeSuisXML, Cookies, fs2) {
+ */
+
+// A RAM FS may be of use here too. Cross-platform, simple to use.
+
+var libpath = require('path'),
+    fs = require('fs'),
+    url = require('url'),
+    //jsgui = require('jsgui3-html'),
+    os = require('os'),
+    http = require('http'),
+    libUrl = require('url'),
+    jsgui = require('jsgui3-html')
+    Resource = jsgui.Resource,
+    Cookies = require('cookies'),
+    fs2 = require('../fs2');
+
+    /*
+
+var stringify = jsgui.stringify,
+    each = jsgui.each,
+    arrayify = jsgui.arrayify,
+    tof = jsgui.tof;
+var filter_map_by_regex = jsgui.filter_map_by_regex;
+var Class = jsgui.Class,
+    Data_Object = jsgui.Data_Object,
+    Enhanced_Data_Object = jsgui.Enhanced_Data_Object;
+var fp = jsgui.fp,
+    is_defined = jsgui.is_defined;
+var Collection = jsgui.Collection;
+*/
+// Extends AutoStart_Resource?
+
+// May need to change around a fair few references to make it workable.
+// May need some more complicated logic to change it to the path for service.
+
+const fnl = require('fnl');
+const obs_or_cb = fnl.obs_or_cb;
+
+const fnlfs = require('fnlfs');
+
+// Cloud_FS_Resource
+// SFTP_FS_Resource
+
+// Publishing an FS resource would enable a directory browsing app.
+//  File_Tree, and connect to the client-side Data_Resource.
+
+const {
+    is_directory, dir_contents
+} = fnlfs;
+
+// This Resource looks to be in a RESTful paradigm. Consider how it would work with GraphQL.
+
+class FS_Resource extends Resource {
+
+    constructor(spec) {
+        super(spec);
+        //this.meta.set('custom_paths', new Data_Object({}));
+        //this.custom_paths = new Data_Object({});
+
+
+        //this.data = {};
+
+        // want to be able to set specific pieces of data to be available.
+        //  This won't be a full DB API, but a starting point for the client-side app to communicate with the server.
+        //  It will interact with a data model through this.
+
+
+        // Could have different types of caching modes too.
+        //  Using fnlfs would be useful too.
+        //  mmfs as a pluggable substitute
+
+        // fnlfs-pro
+
+        this.root_path = spec.root_path || spec.root;
+
+        // can't go below the root path.
+        //  Disallow .. in the given paths.
+
+
+    }
+    // need to promisify this.
+    'start' (callback) {
+        if (callback) {
+            callback(null, true);
+        } else {
+            return true;
+        }
+        
+    }
+
+    'get' (path, callback) {
+        return obs_or_cb((next, complete, error) => {
+
+            (async() => {
+                if (await is_directory(path)) {
+
+                    let full_path = libpath.join(this.root_path, path);
+                    console.log('full_path', full_path);
+
+                    let contents = await dir_contents(full_path);
+                    // however, those are File objects.
+
+                    // try just stringifying them now.
+                    //  No need to handle stringifying here.
+                    complete(contents);
+                } else {
+                    // It's a file.
+                }
+            })();
+        });
+
+        // path is a directory, then return a list of the files there (maybe with metadata)
+        //  nice if we can optionally turn on mmfs but not include it in jsgui itself because it requires ffmpeg / ffprobe.
+        // Could upgrade the FS resource's fs lib.
+        // dir or file
+        // is_directory(path)
+
+        // If it's a file, then it would return a read stream.
+
+
+    }
+    'set' (path, value, callback) {
+        // Overwrite files
+    }
+
+    // Delete
+
+
+
+    /*
+        Does not process HTTP requests itself. Has a Resource_Publisher which contains / refers to this and does the publishing.
+    */
+
+    
+}
+
 module.exports = FS_Resource;