Re: [vos-d] Thinking about Javascript
On Mon, 2007-04-16 at 12:58 -0400, Reed Hedges wrote: > Is anyone here familiar with Javascript much? > Below is a summary about that. > I'm wondering what kind of networking tools are available from > Javascript. IEs 4 Linux Internet Explorer 6, 5.5, 5 on Linux: http://www.tatanka.com.br/ies4linux/page/Main_Page -- JASON A HEBLACK [EMAIL PROTECTED] APT 3(650) 289 - 0954 450 EAST O'KEEFE EAST PALO ALTO, CA 94303 OBJECTIVE Any internship or volunteer position in the computer science industry directed at a career in UNIX, GUI development, digital media, or a related space. SALARY HISTORY 35,000 - 52,000 CERTIFICATES LOCATION 2006 College of San MateoSan Mateo, CA A.S.: Computer & Information Science 2003 UC, Berkeley; University Extension Berkeley, CA Professional Sequence in Java Programming 2002 Sun Microsystems, Inc. Santa Clara, CA Sun Certified Programmer for Java 2 Platform 1999 UC San DiegoLa Jolla, CA B.A.: Visual Arts (Media) EMPLOYMENT LOCATION Macy's West Palo Alto, CA Price Change Associate 2005 - Current Integrated store price changes appropriately thoughout both buildings as a member of the sales support team. College of San Mateo San Mateo, CA Student Senator 2003 - 2004 Attended local school events, meetings, and conferences. Steven Engineering, Inc. South San Francisco, CA Temp 2003 Helped scan literature, file documents, and modify flow charts. paper(media), L.L.C. San Francisco, CA Jr. Technical Assistant 1999 - 2001 o Implemented interactive GUI applications using Internet Explorer and Netscape Navigator. Gained knowledge about layered hyper text markup language widget construction for two and three dimensions. Followed specifications from design documents for routine DHTML template production. Worked with Department Managers, Graphic Designers, Information Architects, and Salespeople to deal with client requests. o Created a menu component for a media asset management effort: http://www.informix.com/media o Visited the client's headquarters and then performed updates: http://www.efax.com/ Consultek Software Systems, Inc. Santa Clara, CA Intern 1992 - 1993 Wrote a file converter using C for proprietary CAD software. SKILLS Perl, HTML/XHTML, CSS, DOM, XML, XSLT, XHR, AJAX, DHTML, SSI, C++, JavaScript, Java, Swing, JSP/Tomcat, JDBC, MySQL, RowSets, Bash, MS-DOS, SSH, Basic, Pascal, MIPS Assembly, LINUX/UNIX. REFERENCES MACY*S HUMAN RESOURCES 1-800-INFOHR1 ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
Re: [vos-d] S5 and single-thread option
On Fri, Apr 20, 2007 at 01:52:39PM -0400, Reed Hedges wrote: > > Pete, in your description of S5 so far it seems like it is defining a > threading model that is not neccesarily coupled to a particular thread > implementation. That is, conceptually vobjects are threads or proceses > but I am guessing that you won't be implementing it by simply creating a > pthread for each vobject :) Does this mean that it will use a thread > pool of some kind? If so, would it be possible to have a thread pool > of size 1, thereby making it possible to run VOS on an OS that > effectively has no threads (I'm thinking of stuff like handheld devices, > phones, embedded systems, whatever). Yes, actually one of my goals is to ensure that the system could be run in a single-threaded mode to be useful for applications like discrete event simulation. For network code we're likely to want to have at least one thread that handles socket activity, but if necessary that could also be something that gets called periodically from the toplevel event loop. Obviously I would like to avoid the recursive-runloop stategy employed by s3, so this will require that all behaviors are written using continuations so that if they have to wait, we can unwind the stack and control can be returned to the top level. But normally there would be a thread pool. Ideally, most of the time most vobjects are "unbound" which means they arn't running on any thread. Vobjects might even be swapped out to the persistance database if they arn't being used. -- [ Peter Amstutz ][ [EMAIL PROTECTED] ][ [EMAIL PROTECTED] ] [Lead Programmer][Interreality Project][Virtual Reality for the Internet] [ VOS: Next Generation Internet Communication][ http://interreality.org ] [ http://interreality.org/~tetron ][ pgpkey: pgpkeys.mit.edu 18C21DF7 ] signature.asc Description: Digital signature ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
[vos-d] s5 scripting (design part 3)
Third in a four part series on major design changes in s5 (What could also be called "VOS Apocalypse") Scripting. One of the things we have encountered over the course of our open source efforts was (obvious in retrospect) people don't like dealing with C++. While there remain compelling reasons to write the VOS "kernel" in C++, for most people the language is hard, setting up a compilation environment is difficult, and there are many things a statically compiled language simply can't do, such as evaluating new code on the fly. With s3 and s4, we have tried to address scripting using the Simplified Wrapper and Interface Generator (SWIG), which is an excelent program which can read C and C++ header files and produce bindings into a variety of popular programming languages. However, this approach suffers from a flaw: by design it is oriented towards calling C/C++ code from other languages. It does not, however, provide much support for allowing your C/C++ code (or other languages hosting in the same system) to call back to that scripting code. So, scripting languages are second-class citizens. What I intend to do in s5 is see to it that all programming languages (scripting or otherwise) can be a first-class citizen in VOS, so that C, C++, Perl, Python, LISP, Java, C# etc code can all call each other, agreeing on the same APIs and data types. The goal, is to allow users to write behaviors and extensions for VOS in their programming language of choice. This is, in some ways, one of the holy grails of computing. How many times has a project been rewritten, or required redundant work, because software A in one language needed to link with software B in another? Now, I don't want to overstate what we're doing, but I do believe that certain key aspects of VOS enable us to produce a cleaner solution than the existing state of the art. There are three key design elements: 1. Actor model for Vobjects and message passing. This is shakes out from the concurrency design discussed earlier. Because Vobjects are required to communicate via message passing, it is easy to add a translation step that converts message parameters from one language datatypes to another. Datatypes will consists of either copyable primitives, or Vobjects, so object references that are communicated between languages are independent identifiers not tied to particular memory (or network) location. Capabilities can be used to enforce security between runtimes (more on that later). Finally, and most importantly, there is no inversion of control inherent when calling on a vobject that is handled by another language. This means that the act of calling from one language to another does not result in the caller's thread being taken over to run the target scripting language runtime or virtual machine, thus avoiding various unintended side effects. If a scripting language runtime or virtual machine is not threadsafe, it can be made to run in a separate, private thread and require that all inbound messages be placed in its message queue. Also useful is in the case that VOS is be incorporated into an existing application or framework, all that is required is that the application's main event loop be able to periodically check for new incoming VOS events. 2. Object Type Definitions (OTDs) for Interfaces Object type definitions describe the messages a vobject accepts and emits, and the child vobjects it might link to. It is similar in spirit to an XML schema or a CORBA interface file, but merges ideas from both. It is independent of programming language, and I am working towards defining the OTD in itself. The primary use of the OTD is input into a code generator that produces concrete classes that implement the marshaling of method parameters into messages, and from messages back to method parameters. Since messages are language-neutral, they can now be passed to a handler written in any other language. For each supported language, we will have either a code generator that produces the required classes, or for more dynamic languages, a module with that uses reflection and evaluation to generate the required classes. The advantage of this is that interfaces can be added to any language runtime at any time without having to modify either the other languages or the C++ kernel. The only essential interface to the C++ kernel will be a minimal C interface designed specifically for the FFI (foreign function interface) feature present used by many languages. This allows most (or all) of the work to be done in the target language that the user is most comfortable in. 3. Runtime extensible object model and reflection Vobjects arn't set in stone. You are free to attach new types, new behaviors and new children onto existing vobjects at any time. This is extremely useful for situations where you need to take several behaviors and smoosh them together into a single vobject (v
[vos-d] S5 and single-thread option
Pete, in your description of S5 so far it seems like it is defining a threading model that is not neccesarily coupled to a particular thread implementation. That is, conceptually vobjects are threads or proceses but I am guessing that you won't be implementing it by simply creating a pthread for each vobject :) Does this mean that it will use a thread pool of some kind? If so, would it be possible to have a thread pool of size 1, thereby making it possible to run VOS on an OS that effectively has no threads (I'm thinking of stuff like handheld devices, phones, embedded systems, whatever). Reed ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
Re: [vos-d] Lindens opening up the Second Life server
Something possibly more interesting to look at is the client announced in Perugia this week at the Web2007 conference. Johannes Behr and Yvonne Jung from Fraunhoeffer demoed a mixed reality client for which they are seeking beta testers. The announcement is up at the www.web3d.org page. The list of node (a mix of X3D and Avalon) is impressive. Apparently they implemented physics with ODE. len From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Amstutz Linden Labs has made another statement that they will soon opening up the server. Not a suprise, but has touched off another wave of speculation about where they're going with it: http://www.3pointd.com/20070328/platforms-and-technologies-panel-at-vw07/ People have pointed out that a number of technologies SL depends on are themselves proprietary (such as the Havoc physics engine) so whatever they release is probably not going to be 100% free software. I think that the strength of VOS going forward (particularly embodied in the new design) will be the ability for the object model to interoperate with other systems on their own terms, so we can still play to the strengths of VOS on either the frontend or backend (depending on the application). The big players in virtual worlds are starting to emerge, but it is still early in the race, and we're in it for the long haul... ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
Re: [vos-d] Metaverse Roadmap
They manage thoughts and ideas toward control attractors.
It is one part Electric Sheep (a content builder for SecondLife) plus the
usual New York VR cabal. SL needs an independent front organization to for
its effort to create a standards patina around their technology. Actually,
this sort of thing can become very serious very fast because it is fueled by
external sources feeding and paying for press. This was done with the W3C
in the early days and used to pirate the status of the legitimate standards
organizations. This works for the company sponsors just as it did for those
who footed the bills for STimBL and crew at MIT.
I call it "The Standards Game". Everyone knows how to play it now. The
thing to pay attention to is the participation agreements that determine by
membership contract what the conditions for contributing intellectual
property are if and when they actually do any real work beyond pontificating
and holding seminars. That is where the rubber meets the road. OTW, yet
another kaffeeklatch and that is fine. Every street corner has a Starbucks.
On the other hand, take a look at that participation list. That is a lot of
luminaries including Castronova and Dyson. These people get on board, raise
money and drain resources to their own pet projects without building too
much. The Venture Capitalists love these guys because they are Judas Goats
for other investors pulling a lot of money toward their interests. Note
the presence of Joi Ito ("content must be free; I must keep my Porsche").
This is a serious bunch though if you look, not a lot of them are building
worlds. They are getting mindshare for the few on that list that do
(Koster, ES, Metaverse, etc.). Castronova was given a MacArthur Genius
Grant to do a project done in VRML ten years ago and already working in JOI.
len
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Peter Amstutz
I've seen it. Honestly I think it's mostly self-serving promotional
fluff by people with vested interests in hyping their technology. I
suppose it's useful from a PR standpoint of promoting immersive 3D, but
it doesn't really offer anything concrete that anyone who might be
interested in building on "metaverse" technology could plan around.
___
vos-d mailing list
vos-d@interreality.org
http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
[vos-d] Lindens opening up the Second Life server
Linden Labs has made another statement that they will soon opening up the server. Not a suprise, but has touched off another wave of speculation about where they're going with it: http://www.3pointd.com/20070328/platforms-and-technologies-panel-at-vw07/ People have pointed out that a number of technologies SL depends on are themselves proprietary (such as the Havoc physics engine) so whatever they release is probably not going to be 100% free software. I think that the strength of VOS going forward (particularly embodied in the new design) will be the ability for the object model to interoperate with other systems on their own terms, so we can still play to the strengths of VOS on either the frontend or backend (depending on the application). The big players in virtual worlds are starting to emerge, but it is still early in the race, and we're in it for the long haul... -- [ Peter Amstutz ][ [EMAIL PROTECTED] ][ [EMAIL PROTECTED] ] [Lead Programmer][Interreality Project][Virtual Reality for the Internet] [ VOS: Next Generation Internet Communication][ http://interreality.org ] [ http://interreality.org/~tetron ][ pgpkey: pgpkeys.mit.edu 18C21DF7 ] signature.asc Description: Digital signature ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
Re: [vos-d] Metaverse Roadmap
I've seen it. Honestly I think it's mostly self-serving promotional fluff by people with vested interests in hyping their technology. I suppose it's useful from a PR standpoint of promoting immersive 3D, but it doesn't really offer anything concrete that anyone who might be interested in building on "metaverse" technology could plan around. On Fri, Apr 20, 2007 at 11:38:15PM +0800, Shun-Yun Hu wrote: > Hello, > > not sure if you guys are aware of this, but thought you might be interested: > > http://www.metaverseroadmap.org/ > > > Shun-Yun > ___ > vos-d mailing list > vos-d@interreality.org > http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d -- [ Peter Amstutz ][ [EMAIL PROTECTED] ][ [EMAIL PROTECTED] ] [Lead Programmer][Interreality Project][Virtual Reality for the Internet] [ VOS: Next Generation Internet Communication][ http://interreality.org ] [ http://interreality.org/~tetron ][ pgpkey: pgpkeys.mit.edu 18C21DF7 ] signature.asc Description: Digital signature ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
[vos-d] Metaverse Roadmap
Hello, not sure if you guys are aware of this, but thought you might be interested: http://www.metaverseroadmap.org/ Shun-Yun ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
