[Building Sakai] New Sakai Architecture

[Gao Jun]

Hi Neal,

Since Sakai become a world-wild software. What about make a Sakai Cloud.

I know there are still a lot of poor people around the world, we cannot 
ignore them.
So, I suggest use RFC 1149 (IP over Avian Carriers)[1] and RFC2549(IP 
over Avian Carriers with Quality of Service)[2] as our communication 
protocol.
If a user has a dove, he/she can use Sakai. When a dove is sent, the 
Sakai CLOUD can be seen immediately.

And, Sakai currently use UTF-8, it has so many disadvantages, one of 
which is it must use 3 bytes to represent a Chinese character.
So, what about use UTF-9, it seems a much powerful encoding.

[1] http://tools.ietf.org/html/rfc1149
[2] http://tools.ietf.org/html/rfc2549
[3] http://tools.ietf.org/html/rfc4042

在 2015年04月01日 19:45, Neal Caidin 写道:
> Hi sakai-dev,
>
> Some discussion in the community about starting Sakai over from scratch.
>
> A couple of the leading architectural suggestions include:
>
> * Writing Sakai completely in Hypercard and using Docker for code 
> distribution to each person's local machine. If necesssary including a 
> 1996 Mac emulator in the bundle. For the occassional "multi-user" 
> version you will need a server to which all the Hypercard stacks are 
> sent, and then use Perl to process the data.
>
> * A DIY kit of 6502 microprocessors for speedy 8 bit processing. Each 
> kit will include a series of 128 pre-programmed ROMs that can be 
> connected in serial to provide the Sakai program. Don't worry, we will 
> not need to write this in Assembly, we will use Cobol on a time share 
> for the development.
>
>
> Other ideas welcome. This is the "brainstorm" stage.
>
> Cheers,
> Neal
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20150402/1aa8f2b0/attachment.html