Nicolas,

I read your specification and I have one question.

I got the idea that the way this would work is that if you used
"flexible" on the client side as well as nekoVM on the server side
that you could write client side code that would seamlessly access
server resources. Is this true?

If it is, then I think you really could be developing what would be a
programming model breakthrough. Currently, I access server code via
openAMF. This is good, but what would be better would be to write
*one* program and to just designate whether a function lives on the
client or the server. If it lives on the client then when that
function is called it calls the server code as a remote procedure
call.

This would mean, in one project, one could write a web based
application where classes have access to different libraries depending
on whether they are client or server classes. But from a programming
perspective, there is no difference between client and server. It
would be as though server code could not "import" client libraries and
vice versa.

Is that what you had in mind?

If not, please consider it because I think this kind of thing could
revolutionize the writing of web applications.

Regards
Hank

On 10/27/05, Nicolas Cannasse <[EMAIL PROTECTED]> wrote:
> Hi folks,
>
> The new still-unamed language specifications have been updated at
> http://ncannasse.free.fr/files/flexible.html . It now includes enumerators,
> Dynamic type parameters and a beginning of grammar rules.
>
> I would like to get comments about the design of the language : what are the
> features you've been dreaming about ? How should look for you the language
> you'll be happy to write in everyday at work ?
>
> It's an open discussion, so bring  your ideas in . I have my own ones, but I
> think opening the design to everybody will result in a better result in the
> end.
>
> Have fun !
>
> Nicolas
>
>
> _______________________________________________
> osflash mailing list
> [email protected]
> http://osflash.org/mailman/listinfo/osflash_osflash.org
>

_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to