As you can tell from my previous messages, I'm not in the marketing phase yet. I'm not armed with competitive information. Websockets are defined by a standard. Any properly implemented websocket server is going to do the same thing and interact in the same way - according to the standard. Serving html pages isn't an area of great diversity either as far as functionality is concerned. There are only a few websocket servers on offer today, so it's possible for people to try all of those that seem like a possible fit to their needs. I expect the eventual integration with HLL to provide both the ultimate in ease of use as well as unlimited potential for the type of applications developed - along with the possibility to scale up to serious commercial use. The bi-directional communication offered by websockets is something my HLL project has been waiting for, for a long, long time. I've previously implemented every other method (long-polling, .......) My websocket server is built in Java and even without doing detailed measurements, I can already see that it's really fast. The code is efficient. I haven't read through the node.js material, so I don't quite know what they mean by "node". (A DOM node? A server hub for distributed applications?) I read just enough to see that they're presenting the idea as a competitive alternative to threads. If anyone can discuss that, perhaps I can respond. Maybe my "HLL" part provides "nodes" (for sophisticated intelligent - even distributed - applications). HLL installations can interact with one another while at the same time providing the higher level logical framework for applications. That's the new trick and my long-winded blogging is a first attempt at introducing the concept. I also use threads. If there is a better alternative to threads for what threads are for, I'm willing to switch. It's only a small part of the code that would be effected. If you're a programmer, then writing application server protocols and other components in your language of choice is probably best (I write in Java). I agree with the node.js folks that the JavaScript engine in Java is now fast and I want to offer that option as an alternative. It just makes sense in this day and age, given the state of the technology. I've been writing frameworks with JavaScript / server code interactions for years. (How many years? I was sad when NetScape went under and still have some of their components in some of my apps. - they were quite serious about JavaScript ...) I've been writing frameworks since back in the days when we called them "toolkits." RE: "The Ghosts in My Machine" - it might have been better had I suggested chapters 2 and 3 rather than 1 and 2. I re-read my chapter 1 this morning and recalled that it just sets the stage - doesn't really respond to the questions (unless you keep reading). But the main point early on is that there are HLL components that will be integrated with my server early (within a couple of weeks) that will make it easier to use - i.e. closer to a finished product than something that just does as much as the standard requires. In particular, even the first alpha release will allow users a relatively simple way to configure applications rather than requiring work in the nuts and bolts to put real applications together. RE: the license. I haven't formalized, but will be happy to do that before the first alpha release, which is still 2-4 weeks away. Anyone who gets involved with this will have a free license that will allow them to use the server free in commercial applications. They'll certainly be able to demo and distribute their code, with the server, as they wish. They will also have first-class technical support for what they're doing - up to and including possible changes to the server code to support their needs. I'm actually most interested in people who want to interact and have a drive to help further the technology based on application development experience. In exchange for all I'm giving at this point, I'm even hoping someone will want to help put together a great demonstration that will show-off my technology with HTML5 web apps. Most definitely, credit would be given where credit is due. --- Den fre 2011-08-26 skrev Roger F. Gay <[email protected]>:
Från: Roger F. Gay <[email protected]> Ämne: Re: [svg-developers] Free WebSocket server / HTML5 (all for you) Till: [email protected] Datum: fredag 26 augusti 2011 20:10 How would it be licensed? Good question. I've offered other software under LGPL, but I haven't decided whether to open source the server. I'll have to formalize it, but the idea of LGPL will remain in all development versions - up to and including when it's really good. You can both develop and integrate into whatever applications you want, and will be able to distribute commercially without any cost. Later versions - I'm not sure. I guess I'll have to say that version 1 or 2 ... maybe somewhere up there I'll try to get paid for my work somehow. But I'll do it in such a way that your effort won't be wasted even if you don't feel you can afford to pay anything, ever, under any circumstances and use it to make money - even if I have to make an exception for you. I'm also quite flexible. Make me a offer. What advantages does it have over node.js? As far as pure websocket and other http serving is concerned, I don't know. I've never even looked at node.js. Maybe the Alphas will tell me. But I'm sure that node.js isn't integrated with HLL, and that's where this is heading. For more on that, you might want to read the three short chapters of "The Ghosts in My Machine" on my blog, starting at:http://highlevellogic.blogspot.com/2010/10/ghosts-in-my-machine-chapter-1.html --- Den fre 2011-08-26 skrev Jacob Beard <[email protected]>: Från: Jacob Beard <[email protected]> Ämne: Re: [svg-developers] Free WebSocket server / HTML5 (all for you) Till: [email protected] Datum: fredag 26 augusti 2011 19:50 Two quick questions: 1. How would it be licensed? 2. What advantages would it have over node.js? Jake [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] ------------------------------------ ----- To unsubscribe send a message to: [email protected] -or- visit http://groups.yahoo.com/group/svg-developers and click "edit my membership" ----Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/svg-developers/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/svg-developers/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
