Yes, I remember talk of dbus! Any progress Shawn? I am actually doing what you describe now and embedding Chicken to C to handle s-expressions and bit stuffing them (packedobjects). I was curious though to examine ways of removing the dependency of Chicken from the graphical client and using dbus to communicate with another entity that handles the s-expressions. Removing Chicken would simplify building the graphical client on the mobile. The problem is just moved to another place and hidden from C developers who could focus on the client. If that makes sense.
Regards, John. On 14/02/2008, Elf <[EMAIL PROTECTED]> wrote: > > > hm. i realised i didnt respond to your original question. iirc, shawn > rutelege proposed something about a dbus egg a few months ago. i dont know > what became of it. > > another possibility, if youre dealing with deeply nested structures: > install chicken on the servers as well. use the embedded chicken interface > from c (if you need to keep it in c) to handle the chicken messages and > translate them into something more easily understandable. > > > -elf > > On Thu, 14 Feb 2008, john wrote: > > > Hi Elf, thanks for the quick response... > > > > a) The protocol might not be simple it may be complex nested > > structures. I don't want to write my own parser in C. There is a C > > s-expr library out there though. > > b) Not sure what this is? > > c) XML is evil :) I have tried to compress XML without great results. > > Assume each bit counts in this application. > > > > On 14/02/2008, Elf <[EMAIL PROTECTED]> wrote: > >> > >> quick question, which may be a really stupid question cause im not sure > >> im understanding properly... > >> > >> why not do one of the following: > >> a) simple string-encoded sexprs to the mobile client, some kind of > >> well-formed message to the server? (ie, different format based on > >> communication direction, playing to both sides strong points) > >> b) define a simple DS message format or lang and use this? > >> c) pass around xml? > >> > >> -elf > >> > >> > >> On Thu, 14 Feb 2008, john wrote: > >> > >> > I have not had a chance to properly think this idea through yet but > >> > thought I would throw it out to the lions (chickens) for some > >> > feedback. > >> > > >> > In a mobile client application I am developing I currently embed > >> > Chicken into Gtk+. The client communicates with 2 servers. One > >> > connection uses plain s-expressions the other uses binary encoded > >> > s-expressions. This works fine but does add complication to the > >> > client. > >> > > >> > In the embedded Linux world D-Bus seems a popular inter-process > >> > communication tool (http://en.wikipedia.org/wiki/D-Bus). > >> > > >> > So I was wondering if it is feasible to develop some kind of > >> > s-expression based daemon which talks D-Bus. The Gtk+ client(s) can > >> > then talk dbus to send/receive data. The s-expression daemon mux's the > >> > communication to external TCP servers using s-expression based > >> > protocols. The client will then not need to have Chicken embedded and > >> > can use the in-built D-Bus features of glib. Ideally the s-expression > >> > mux'er could be configured to switch between binary and text encoding > >> > depending on requirements. Or even perhaps throttle traffic or try and > >> > limit costs over an expensive mobile link. > >> > > >> > So any feedback on the idea appreciated, > >> > > >> > John. > >> > > >> > > >> > >>> _______________________________________________ > >> > Chicken-users mailing list > >> > [email protected] > >> > http://lists.nongnu.org/mailman/listinfo/chicken-users > >> > > >> > > > _______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
