Buzzen Non Socket Connection

A few people have asked me about a non socket connection for Buzzen. I put this together in a few minutes.

Hopefully I made it so it's easily understandable. I could have made it smaller but i want ppl to be able to build their own from this example.

Anyone want to improve on it and post it feel free. No credit to me is needed. I do ask that you leave the credit to nick for his regex snippet in however.

sBuzzconn.txt

Well i thought i would add my 2 sencse in to this part of the topic as well many diffrent connectors out there now and alot are socket based and well as much as we like sockets some times its also good to have something diffrent, thats where i want to just let every one know that i am working on a sockless connector my self which will be available for download hopefully some time in the next fiew months,i am just ironing out all the bugs in it and making it work as it should,when its done i hope to have it hosted on tg downloads if thats ok with err0r of course and it does have its own site as well i will keep every one posted on the progress and hopefully it will be out soon.

At the moment it is being tested while its being worked on and i will also get some of its testers to post here about it and get them to tell you what they think of this connector.

look forward to seeing it

ok,as soon as im ready for it to be tested i will let you know then thoes that want to test it and see how it works for them will be more than welcome to do so,at the moment its still in the development stages and still has on going work to it,im just coding the access lister and a fiew other items,and thanks to err0r i have had alot of sucsess with the connector so far,managed to take it past the basic connector it was 4 weeks ago.

so thanks again err0r

np helping makes the community stronger

i have been testing vade connector since it was first coded in the soulfly room and since then the results of the updates have been realy well designed,although the connector is still in construction its a must have for any scripter.

PS when he is done i'm going to be pestering the hell out of him til he add colors in it

well as for collors thats something i will try to add in but may need help doing,i havent realy got that far knowladge wise so most of whats beeing added is code that i am learning so at this point im not going to add them in,how ever if any one dos have any thing they would like to see in it they can post them at the following site vade connector website(idea's link) and i will do my best to add what is requested

I'll probably start work on some addons for this, lol. Thanks, err0r.

np, be nice to see some activity again lol

well i have just got my pc back again and i am continueing work on vade to get it where it should be however some itemes i have come accross seem to be harder to code than i expected but this whont put me off from getting this connector complete and in working order, i know it will take time for me to do this con but the best things seem to be the slow things,only one problem i came accross and cant seem to fix is that it whont recognise text from the soulfly connector so if any of you have any ideas or thoughts on this i would love to here them

Regards Knightrider

Won't recognize a text event when the nick is using soulfly?

SoulFly should mimic webchat, so text sent should look just like webchat.

he wasn't accounting for the [style tags in his connection.. it's sorted now

yea travis it wasent letting any one using soulfy use its commands eg !owner ect due to stye tags but thanks to err0r its fixed now and hopefully not a problem any more,just the case of doing a new form for code but no major changes.

as for everything else it is all working as it should

hi every one,im just letting you all know im still working on vade its taking longer than i expected due to problems in my personal life but im hoping to have the beta version out befour december 23rd this year,i was hoping that i could have it done sooner but with all thats going on its proveing impossable but just so you know the work is still on going.

I have a question. What's the difference between a socket and non-socket connection? Are they any better versus each other?

A non socket connection is normal mirc. It uses the /server command to connect to the server. mIRC handles all the events like text, join, part etc.

A socket connection connects to the server using a socket. /sockopen, /sockread

When you do this the person writing the connection needs to translate most events to mirc.

There are pros and cons to both. On buzzen there are some features you wont be able to use using normal mirc connection. The overall speed really depends on the scripter's knowledge and skill, but generally it is faster to use normal mIRC.

Using a socket to connect allows more freedom. You process the events before mIRC does and then send them to mIRC.

what features can you not use when you choose to use a non socket conn for buzzen?

Clientmode CD1

Seeing profile info on nicks.

you can do that on non sock.. just send raw CLIENTMODE cd1 once you are connected to a room and it will switch.. after you get the info you can unset it with raw clientmode again.. while it is easier with a socket conn because of joining rooms while in clientmode cd1 with a socket conn it can still be done in a non socket conn.

I think both ways are just as effective. I choose the non socket method because i prefer to use my script over multiple networks.. while at one time i did have a socket conn for two servers in my script and was able to connect everywhere i go it's just easier for me to not use a socket conn at all.

like travis said there are pros and cons to each. anything is possible with either with the right coding. I don't see that there are any limitations to either. Each has their own unique workarounds for things.

Well why didnt you just say that in the first place?

I thought you had to set clientmode before you connected.