That's pretty much what I was wondering. I was hoping that I could get a skeleton app that I'd just fill in the blanks but it works either way I guess.
On Thu, Oct 30, 2008 at 21:11, Ted Dunning <[EMAIL PROTECTED]> wrote: > Hannes, > > I can't comment on the Erlang example, but in general with thrift, the > generated code defines an interface that you have to implement. > > When you start the server, you pass your implementation of the > functionality > to the server and it handles the RPC (using generated code). Thus, I would > think that server.erl implements the server functions as you say while the > code in gen-erl is the server infrastructure that calls out to server.erl > > This design is in contrast to systems that require you to edit the > generated > code and has what I think are very clear advantages. > > On Thu, Oct 30, 2008 at 2:05 PM, Hannes Baldursson <[EMAIL PROTECTED] > >wrote: > > > Hi all, > > > > I'm having some troubles with the Erlang generated code from Thrift. I > > might > > add that I'm a newbie in using Thrift and got minimal knowledge about > > Erlang > > but I'm fairly experienced in programming. > > > > I've been looking at the tutorial where in one directory "tutorial/erl/" > > there are files called "server.erl" and "server.sh" that seem to be an > > implementation of the RPC functions. Am I missing something or doesn't > > Thrift generate server stubs based on my definition file? > > > > All the generated files I see are in the gen-erl and I can't see that any > > one of them do what server.erl does... am I missing something or do I > have > > to hand code the "server.erl" file > > > > btw, I will make sure to add your points into the wiki page > > > > Thanks in advance, > > Hannes Baldursson > > > > > > -- > ted >
