1. How about a plug-in architecture to the VM which takes code specifically designed for graphics primatives which have been put in the code. The idea of plug-in is a lot more fine grained than what you're saying.
2. LISP is a great example. It is the first example that people present. Ashame that LISP has such terrible syntax. Wouldn't it be nice to have an editor that displays code at a higher level, but the low level language is like LISP. Putting code in a different form allows that. I'm looking at doing a language in Argot ( http://www.einet.com.au/ ) which is binary. It will probably act a lot like LISP but will look like a format that the user is comfortable.
3. I disagree. Grammars and parsers are a pain to write. And grammars are especially hard to develop and get right. A format which is closer to AST is easier to parse. If we're going to get rid of this tower of babel we've developed for ourselves, we need to develop more flexible formats to describe code.
Look through the site ps2dev.org and you'll find a huge amount of information and tools required to program your ps2. Check the loaders section and look at ps2link.. look at ps2lib.. see the various graphics libraries available including two openGL implementations. Look at the various sound players.. look at the tcpip stack that runs on the ethernet adapter. All the source code is there and ready to use. Check out www.thethirdcreation.net and look at the demos that have already been done.
The real hard work of getting stuff together has been done. Now we just need more people writing programs for the PS2.
It's true. There has been very little research done in RPC mechanisms. In November I attended three different conferences (two on distributed computing) to see what work was being done. Most research is in either building on top of CORBA or XML and web services. Infact, I was disapointed at the lack of research in the low level guts of RPC mechanisms.
The reason I attended the conferences is that I have spent a lot of time developing a binary RPC mechanism. The method I use can be used in messages (eg MQSeries) or over TCP or UDP or whatever other connection mechanism you feel like.
It fulfills: 1. object oriented Its currently implemented in java, and allows basic data types, objects and streams to be sent between client and server. 2. extensible Any object can be sent between client and server, and the programming paradigm is simple. 3. platform independent Currently written in java, with implementation for C++ and.Net on the todo list. 4. supports signatures.. Not yet. This is an additional layer which could be quickly added into the communication stack. I haven't had a need for it yet, so haven't been interested in implementing anything like it. 5. privacy as above. Simple solution is to use SSL as the connection layer. 6. time sensitive simple timeouts are easy to implement, however this hints at other issues which is a big can of worms. ie Was the task completed on the server? 7. bandwidth efficency pure binary with very small overhead
The negatives are that its not available yet. We are currently working out licensing issues. Sorry, this isn't open source. More information will be made available over the next month or two.
A small hint at what Colony can do is at www.livemedia.com.au
Slashdot Mirror
2. LISP is a great example. It is the first example that people present. Ashame that LISP has such terrible syntax. Wouldn't it be nice to have an editor that displays code at a higher level, but the low level language is like LISP. Putting code in a different form allows that. I'm looking at doing a language in Argot ( http://www.einet.com.au/ ) which is binary. It will probably act a lot like LISP but will look like a format that the user is comfortable.
3. I disagree. Grammars and parsers are a pain to write. And grammars are especially hard to develop and get right. A format which is closer to AST is easier to parse. If we're going to get rid of this tower of babel we've developed for ourselves, we need to develop more flexible formats to describe code.
Look through the site ps2dev.org and you'll find a huge amount of information and tools required to program your ps2. Check the loaders section and look at ps2link.. look at ps2lib.. see the various graphics libraries available including two openGL implementations. Look at the various sound players.. look at the tcpip stack that runs on the ethernet adapter. All the source code is there and ready to use. Check out www.thethirdcreation.net and look at the demos that have already been done. The real hard work of getting stuff together has been done. Now we just need more people writing programs for the PS2.
It's true. There has been very little research done in RPC mechanisms. In November I attended three different conferences (two on distributed computing) to see what work was being done. Most research is in either building on top of CORBA or XML and web services. Infact, I was disapointed at the lack of research in the low level guts of RPC mechanisms.
.Net on the todo list.
The reason I attended the conferences is that I have spent a lot of time developing a binary RPC mechanism. The method I use can be used in messages (eg MQSeries) or over TCP or UDP or whatever other connection mechanism you feel like.
It fulfills:
1. object oriented
Its currently implemented in java, and allows basic data types, objects and streams to be sent between client and server.
2. extensible
Any object can be sent between client and server, and the programming paradigm is simple.
3. platform independent
Currently written in java, with implementation for
C++ and
4. supports signatures..
Not yet. This is an additional layer which could be quickly added into the communication stack. I haven't had a need for it yet, so haven't been interested in implementing anything like it.
5. privacy
as above. Simple solution is to use SSL as the connection layer.
6. time sensitive
simple timeouts are easy to implement, however this hints at other issues which is a big can of worms. ie Was the task completed on the server?
7. bandwidth efficency
pure binary with very small overhead
The negatives are that its not available yet. We are currently working out licensing issues. Sorry, this isn't open source. More information will be made available over the next month or two.
A small hint at what Colony can do is at www.livemedia.com.au