Thread: [sstorm-discuss] Re: Perl server
Status: Beta
Brought to you by:
idanso
From: Idan S. <i_...@ya...> - 2001-06-13 21:19:16
|
use Active::Client; $a=Active::Client->new(); $a->setCompoment("my.component","/RPC2","localhost","4030"); I know this is a bit complex to do. For python, I've written some classes that simplify these things. I myself not a big fan of perl, but I'm willing to accept similiar contributions:) -- Idan |
From: Steven <cr...@dt...> - 2001-06-13 23:24:47
|
Actually, I don't mind what that is doing. I now have python calling to my standalone perl app. It is taking a bit of work to remember that since some of the core code for the API is in python I have to move stop quoting the numbers as arguments. I have been so used to quoting numbers going into SQL statements, and perl will auto convert to what you need when you need it. I refuse to get into a langauage war. I know quite a few already, and if there becomes any free time, I might see if I can port the libraries to use in other languages. It would be fun to be able to put this square up against .NET and all that from MS. Well, time to head home and play with this some more. BTW, I saw comments in the libs about a modified Frontier::RPC2. Is there new development going on there? I would like to see, and therefore may code it myself, a way to dynamically add functions to the Daemon without stoping and restarting it. Shouldn't be too dificult, but I will browse the code tonight for that functionality. Steven On Wed, Jun 13, 2001 at 10:16:27PM +0300, Idan Sofer wrote: > use Active::Client; > > $a=Active::Client->new(); > $a->setCompoment("my.component","/RPC2","localhost","4030"); > > I know this is a bit complex to do. For python, I've written some > classes that simplify these things. I myself not a big fan of perl, but > I'm willing to accept similiar contributions:) > > > > -- > > > Idan > > > > _______________________________________________ > Sstorm-discuss mailing list > Sst...@li... > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss |
From: Michael H. <Mic...@pd...> - 2001-06-14 01:01:31
|
Steven-- Greetings, I am Michael Hay, and the replacement for Frontier::RPC2 I am working on. Although, since it is a when I have the time kind of effort progress is slooooowwwww... I can do some simple clean ups, and if you would be willing to help, I can mail you the part which I am working on now to see if between the two of us we can hasten development of this part. Let me know if you are interested! Michael Steven writes: > Actually, I don't mind what that is doing. I now have python calling to my > standalone perl app. It is taking a bit of work to remember that since some of > the core code for the API is in python I have to move stop quoting the numbers > as arguments. I have been so used to quoting numbers going into SQL statements, > and perl will auto convert to what you need when you need it. > > I refuse to get into a langauage war. I know quite a few already, and if there > becomes any free time, I might see if I can port the libraries to use in other > languages. It would be fun to be able to put this square up against .NET and > all that from MS. > > Well, time to head home and play with this some more. > > BTW, I saw comments in the libs about a modified Frontier::RPC2. Is there new > development going on there? I would like to see, and therefore may code it > myself, a way to dynamically add functions to the Daemon without stoping and > restarting it. Shouldn't be too dificult, but I will browse the code tonight > for that functionality. > > Steven > > On Wed, Jun 13, 2001 at 10:16:27PM +0300, Idan Sofer wrote: > > use Active::Client; > > > > $a=Active::Client->new(); > > $a->setCompoment("my.component","/RPC2","localhost","4030"); > > > > I know this is a bit complex to do. For python, I've written some > > classes that simplify these things. I myself not a big fan of perl, but > > I'm willing to accept similiar contributions:) > > > > > > > > -- > > > > > > Idan > > > > > > > > _______________________________________________ > > Sstorm-discuss mailing list > > Sst...@li... > > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss > > _______________________________________________ > Sstorm-discuss mailing list > Sst...@li... > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss |
From: Steven <cr...@dt...> - 2001-06-14 07:44:48
|
This sounds great. If you want to point me in the right direction to where to pick a current version of what you have been working on, I'll see what I can help out on. Also if you like, post a list of the features you are trying to add/improve so that once I get the couple new functions I must have, I can swing back around and help you out with what you need. Lucky for me, most of my development will be work related, since this looks VERY promising to be incorporated into our main app at work. I also love the fact that my boss like the idea of us being able to contribute back to open source projects when it helps the company out, and the rest of the owners pretty much agree. Steven On Wed, Jun 13, 2001 at 11:54:22PM +0000, Michael Hay wrote: > Steven-- > > Greetings, I am Michael Hay, and the replacement for Frontier::RPC2 I am > working on. Although, since it is a when I have the time kind of effort > progress is slooooowwwww... I can do some simple clean ups, and if you > would be willing to help, I can mail you the part which I am working on now > to see if between the two of us we can hasten development of this part. > > Let me know if you are interested! > > Michael > > Steven writes: > > > Actually, I don't mind what that is doing. I now have python calling to my > > standalone perl app. It is taking a bit of work to remember that since some of > > the core code for the API is in python I have to move stop quoting the numbers > > as arguments. I have been so used to quoting numbers going into SQL statements, > > and perl will auto convert to what you need when you need it. > > > > I refuse to get into a langauage war. I know quite a few already, and if there > > becomes any free time, I might see if I can port the libraries to use in other > > languages. It would be fun to be able to put this square up against .NET and > > all that from MS. > > > > Well, time to head home and play with this some more. > > > > BTW, I saw comments in the libs about a modified Frontier::RPC2. Is there new > > development going on there? I would like to see, and therefore may code it > > myself, a way to dynamically add functions to the Daemon without stoping and > > restarting it. Shouldn't be too dificult, but I will browse the code tonight > > for that functionality. > > > > Steven > > > > On Wed, Jun 13, 2001 at 10:16:27PM +0300, Idan Sofer wrote: > > > use Active::Client; > > > > > > $a=Active::Client->new(); > > > $a->setCompoment("my.component","/RPC2","localhost","4030"); > > > > > > I know this is a bit complex to do. For python, I've written some > > > classes that simplify these things. I myself not a big fan of perl, but > > > I'm willing to accept similiar contributions:) > > > > > > > > > > > > -- > > > > > > > > > Idan > > > > > > > > > > > > _______________________________________________ > > > Sstorm-discuss mailing list > > > Sst...@li... > > > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss > > > > _______________________________________________ > > Sstorm-discuss mailing list > > Sst...@li... > > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss > > _______________________________________________ > Sstorm-discuss mailing list > Sst...@li... > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss |
From: Michael H. <Mic...@pd...> - 2001-06-14 17:41:13
|
Steven writes: Will do, I will come up with a feature list and try to mail that to you today along with the working module. Essentially what I am working on now is getting full XML-RPC compliance. My current intent is using XML::Simple to transform XML data into Perl data and vice versa. I do not know if this is fully possible, but it is worth a shot. Michael > This sounds great. If you want to point me in the right direction to where to > pick a current version of what you have been working on, I'll see what I can > help out on. Also if you like, post a list of the features you are trying to > add/improve so that once I get the couple new functions I must have, I can > swing back around and help you out with what you need. Lucky for me, most of my > development will be work related, since this looks VERY promising to be > incorporated into our main app at work. I also love the fact that my boss like > the idea of us being able to contribute back to open source projects when it > helps the company out, and the rest of the owners pretty much agree. > > Steven > > On Wed, Jun 13, 2001 at 11:54:22PM +0000, Michael Hay wrote: > > Steven-- > > > > Greetings, I am Michael Hay, and the replacement for Frontier::RPC2 I am > > working on. Although, since it is a when I have the time kind of effort > > progress is slooooowwwww... I can do some simple clean ups, and if you > > would be willing to help, I can mail you the part which I am working on now > > to see if between the two of us we can hasten development of this part. > > > > Let me know if you are interested! > > > > Michael > > > > Steven writes: > > > > > Actually, I don't mind what that is doing. I now have python calling to my > > > standalone perl app. It is taking a bit of work to remember that since some of > > > the core code for the API is in python I have to move stop quoting the numbers > > > as arguments. I have been so used to quoting numbers going into SQL statements, > > > and perl will auto convert to what you need when you need it. > > > > > > I refuse to get into a langauage war. I know quite a few already, and if there > > > becomes any free time, I might see if I can port the libraries to use in other > > > languages. It would be fun to be able to put this square up against .NET and > > > all that from MS. > > > > > > Well, time to head home and play with this some more. > > > > > > BTW, I saw comments in the libs about a modified Frontier::RPC2. Is there new > > > development going on there? I would like to see, and therefore may code it > > > myself, a way to dynamically add functions to the Daemon without stoping and > > > restarting it. Shouldn't be too dificult, but I will browse the code tonight > > > for that functionality. > > > > > > Steven > > > > > > On Wed, Jun 13, 2001 at 10:16:27PM +0300, Idan Sofer wrote: > > > > use Active::Client; > > > > > > > > $a=Active::Client->new(); > > > > $a->setCompoment("my.component","/RPC2","localhost","4030"); > > > > > > > > I know this is a bit complex to do. For python, I've written some > > > > classes that simplify these things. I myself not a big fan of perl, but > > > > I'm willing to accept similiar contributions:) > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > Idan > > > > > > > > > > > > > > > > _______________________________________________ > > > > Sstorm-discuss mailing list > > > > Sst...@li... > > > > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss > > > > > > _______________________________________________ > > > Sstorm-discuss mailing list > > > Sst...@li... > > > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss > > > > _______________________________________________ > > Sstorm-discuss mailing list > > Sst...@li... > > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss > > _______________________________________________ > Sstorm-discuss mailing list > Sst...@li... > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss |
From: Steven <cr...@dt...> - 2001-06-15 17:17:50
|
Well, I just found out that the feature I thought needed to get added, didn't. I didn't realize that when instatiating the Frontier::Daemon, it was passed a reference to a hash of methods. This reference takes care of methods added after the daemon started. I have to admit that looking through the different modules definately helped me figure out a bit more about perl. On Thu, Jun 14, 2001 at 04:33:42PM +0000, Michael Hay wrote: > Steven writes: > > Will do, I will come up with a feature list and try to mail that to you > today along with the working module. Essentially what I am working on now > is getting full XML-RPC compliance. My current intent is using XML::Simple > to transform XML data into Perl data and vice versa. I do not know if this > is fully possible, but it is worth a shot. > > Michael > > > > This sounds great. If you want to point me in the right direction to where to > > pick a current version of what you have been working on, I'll see what I can > > help out on. Also if you like, post a list of the features you are trying to > > add/improve so that once I get the couple new functions I must have, I can > > swing back around and help you out with what you need. Lucky for me, most of my > > development will be work related, since this looks VERY promising to be > > incorporated into our main app at work. I also love the fact that my boss like > > the idea of us being able to contribute back to open source projects when it > > helps the company out, and the rest of the owners pretty much agree. > > > > Steven > > > > On Wed, Jun 13, 2001 at 11:54:22PM +0000, Michael Hay wrote: > > > Steven-- > > > > > > Greetings, I am Michael Hay, and the replacement for Frontier::RPC2 I am > > > working on. Although, since it is a when I have the time kind of effort > > > progress is slooooowwwww... I can do some simple clean ups, and if you > > > would be willing to help, I can mail you the part which I am working on now > > > to see if between the two of us we can hasten development of this part. > > > > > > Let me know if you are interested! > > > > > > Michael > > > > > > Steven writes: > > > > > > > Actually, I don't mind what that is doing. I now have python calling to my > > > > standalone perl app. It is taking a bit of work to remember that since some of > > > > the core code for the API is in python I have to move stop quoting the numbers > > > > as arguments. I have been so used to quoting numbers going into SQL statements, > > > > and perl will auto convert to what you need when you need it. > > > > > > > > I refuse to get into a langauage war. I know quite a few already, and if there > > > > becomes any free time, I might see if I can port the libraries to use in other > > > > languages. It would be fun to be able to put this square up against .NET and > > > > all that from MS. > > > > > > > > Well, time to head home and play with this some more. > > > > > > > > BTW, I saw comments in the libs about a modified Frontier::RPC2. Is there new > > > > development going on there? I would like to see, and therefore may code it > > > > myself, a way to dynamically add functions to the Daemon without stoping and > > > > restarting it. Shouldn't be too dificult, but I will browse the code tonight > > > > for that functionality. > > > > > > > > Steven > > > > > > > > On Wed, Jun 13, 2001 at 10:16:27PM +0300, Idan Sofer wrote: > > > > > use Active::Client; > > > > > > > > > > $a=Active::Client->new(); > > > > > $a->setCompoment("my.component","/RPC2","localhost","4030"); > > > > > > > > > > I know this is a bit complex to do. For python, I've written some > > > > > classes that simplify these things. I myself not a big fan of perl, but > > > > > I'm willing to accept similiar contributions:) > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > > Idan > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Sstorm-discuss mailing list > > > > > Sst...@li... > > > > > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss > > > > > > > > _______________________________________________ > > > > Sstorm-discuss mailing list > > > > Sst...@li... > > > > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss > > > > > > _______________________________________________ > > > Sstorm-discuss mailing list > > > Sst...@li... > > > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss > > > > _______________________________________________ > > Sstorm-discuss mailing list > > Sst...@li... > > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss > > _______________________________________________ > Sstorm-discuss mailing list > Sst...@li... > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss |
From: Michael H. <Mic...@pd...> - 2001-06-14 22:43:44
|
Steve-- I haven't much time... Anyway the package is attached. XML::RPC::CODEC is the primary work effort to date. Right now my short term goal is to replace the existing XML::RPC::encode_*/decode_* methods with XML-RPC compliant logic from XML::RPC::CODEC (which should one day be is own standalone package...). So take a look, and I will send a little more information later on. Michael Steven writes: > This sounds great. If you want to point me in the right direction to where to > pick a current version of what you have been working on, I'll see what I can > help out on. Also if you like, post a list of the features you are trying to > add/improve so that once I get the couple new functions I must have, I can > swing back around and help you out with what you need. Lucky for me, most of my > development will be work related, since this looks VERY promising to be > incorporated into our main app at work. I also love the fact that my boss like > the idea of us being able to contribute back to open source projects when it > helps the company out, and the rest of the owners pretty much agree. > > Steven > > On Wed, Jun 13, 2001 at 11:54:22PM +0000, Michael Hay wrote: > > Steven-- > > > > Greetings, I am Michael Hay, and the replacement for Frontier::RPC2 I am > > working on. Although, since it is a when I have the time kind of effort > > progress is slooooowwwww... I can do some simple clean ups, and if you > > would be willing to help, I can mail you the part which I am working on now > > to see if between the two of us we can hasten development of this part. > > > > Let me know if you are interested! > > > > Michael > > > > Steven writes: > > > > > Actually, I don't mind what that is doing. I now have python calling to my > > > standalone perl app. It is taking a bit of work to remember that since some of > > > the core code for the API is in python I have to move stop quoting the numbers > > > as arguments. I have been so used to quoting numbers going into SQL statements, > > > and perl will auto convert to what you need when you need it. > > > > > > I refuse to get into a langauage war. I know quite a few already, and if there > > > becomes any free time, I might see if I can port the libraries to use in other > > > languages. It would be fun to be able to put this square up against .NET and > > > all that from MS. > > > > > > Well, time to head home and play with this some more. > > > > > > BTW, I saw comments in the libs about a modified Frontier::RPC2. Is there new > > > development going on there? I would like to see, and therefore may code it > > > myself, a way to dynamically add functions to the Daemon without stoping and > > > restarting it. Shouldn't be too dificult, but I will browse the code tonight > > > for that functionality. > > > > > > Steven > > > > > > On Wed, Jun 13, 2001 at 10:16:27PM +0300, Idan Sofer wrote: > > > > use Active::Client; > > > > > > > > $a=Active::Client->new(); > > > > $a->setCompoment("my.component","/RPC2","localhost","4030"); > > > > > > > > I know this is a bit complex to do. For python, I've written some > > > > classes that simplify these things. I myself not a big fan of perl, but > > > > I'm willing to accept similiar contributions:) > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > Idan > > > > > > > > > > > > > > > > _______________________________________________ > > > > Sstorm-discuss mailing list > > > > Sst...@li... > > > > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss > > > > > > _______________________________________________ > > > Sstorm-discuss mailing list > > > Sst...@li... > > > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss > > > > _______________________________________________ > > Sstorm-discuss mailing list > > Sst...@li... > > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss > > _______________________________________________ > Sstorm-discuss mailing list > Sst...@li... > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss |
From: Michael H. <Mic...@pd...> - 2001-06-15 02:17:16
|
Okay here is a more detailed listing as promised: Why XML::RPC with RPC::XML, SOAP::Lite and Frontier::RPC2 out there? Well, my goal for XML::RPC is to unbind the transport layer from the encoding layer. This entails XML::RPC::CODEC being the real package behind every thing. With all of the packages mentioned above there is some level of dependance on HTTP::Daemon or Net::Daemon. When considering agent or standalone technology, low levels of dependancies and small foot print are critical. This is my reasoning for XML::RPC and all modules residing in child name spaces. Now onto the features... XML::RPC -- o change encode_call/decode_call and encode_response/decode_response to use an analog in XML::RPC::CODEC. o create internal registry logic which meshes with SandStorm, and allows for the wrapping of any perl module/package o enhance and create a module access control listing which limits the availability of any perl package o add some form of encryption mechanism for all transactions (SSL?) o create a sample threaded server XML::RPC::CODEC -- o get full XML-RPC compliance -make _get_params work -add support for complex XML data structures (arrays of structs , and structs of arrays, etc.) -make the module capable of native bin64 encode/decode -expose array, boolean, string, real, etc. to calling programs -fully document with POD -decouple from XML::RPC package, and create new package So this is a quick snapshot, I will think on this a little more, and come up with more features/formality. Michael Michael Hay writes: > Steve-- > > I haven't much time... Anyway the package is attached. XML::RPC::CODEC is > the primary work effort to date. Right now my short term goal is to > replace the existing XML::RPC::encode_*/decode_* methods with XML-RPC > compliant logic from XML::RPC::CODEC (which should one day be is own > standalone package...). So take a look, and I will send a little more > information later on. > > Michael > > Steven writes: > > > This sounds great. If you want to point me in the right direction to where to > > pick a current version of what you have been working on, I'll see what I can > > help out on. Also if you like, post a list of the features you are trying to > > add/improve so that once I get the couple new functions I must have, I can > > swing back around and help you out with what you need. Lucky for me, most of my > > development will be work related, since this looks VERY promising to be > > incorporated into our main app at work. I also love the fact that my boss like > > the idea of us being able to contribute back to open source projects when it > > helps the company out, and the rest of the owners pretty much agree. > > > > Steven > > > > On Wed, Jun 13, 2001 at 11:54:22PM +0000, Michael Hay wrote: > > > Steven-- > > > > > > Greetings, I am Michael Hay, and the replacement for Frontier::RPC2 I am > > > working on. Although, since it is a when I have the time kind of effort > > > progress is slooooowwwww... I can do some simple clean ups, and if you > > > would be willing to help, I can mail you the part which I am working on now > > > to see if between the two of us we can hasten development of this part. > > > > > > Let me know if you are interested! > > > > > > Michael > > > > > > Steven writes: > > > > > > > Actually, I don't mind what that is doing. I now have python calling to my > > > > standalone perl app. It is taking a bit of work to remember that since some of > > > > the core code for the API is in python I have to move stop quoting the numbers > > > > as arguments. I have been so used to quoting numbers going into SQL statements, > > > > and perl will auto convert to what you need when you need it. > > > > > > > > I refuse to get into a langauage war. I know quite a few already, and if there > > > > becomes any free time, I might see if I can port the libraries to use in other > > > > languages. It would be fun to be able to put this square up against .NET and > > > > all that from MS. > > > > > > > > Well, time to head home and play with this some more. > > > > > > > > BTW, I saw comments in the libs about a modified Frontier::RPC2. Is there new > > > > development going on there? I would like to see, and therefore may code it > > > > myself, a way to dynamically add functions to the Daemon without stoping and > > > > restarting it. Shouldn't be too dificult, but I will browse the code tonight > > > > for that functionality. > > > > > > > > Steven > > > > > > > > On Wed, Jun 13, 2001 at 10:16:27PM +0300, Idan Sofer wrote: > > > > > use Active::Client; > > > > > > > > > > $a=Active::Client->new(); > > > > > $a->setCompoment("my.component","/RPC2","localhost","4030"); > > > > > > > > > > I know this is a bit complex to do. For python, I've written some > > > > > classes that simplify these things. I myself not a big fan of perl, but > > > > > I'm willing to accept similiar contributions:) > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > > Idan > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Sstorm-discuss mailing list > > > > > Sst...@li... > > > > > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss > > > > > > > > _______________________________________________ > > > > Sstorm-discuss mailing list > > > > Sst...@li... > > > > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss > > > > > > _______________________________________________ > > > Sstorm-discuss mailing list > > > Sst...@li... > > > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss > > > > _______________________________________________ > > Sstorm-discuss mailing list > > Sst...@li... > > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss > > _______________________________________________ > Sstorm-discuss mailing list > Sst...@li... > http://lists.sourceforge.net/lists/listinfo/sstorm-discuss |